https://google.com

Main metrics

89

Performance

91

SEO

87

Accessibility

100

Best practices

Largest Contentful Paint 3.1 s
First Contentful Paint 1.8 s
Total Blocking Time 170 ms
Cumulative Layout Shift 0.009
Thumbnail

Traffic & global rank (estimates)

  • Global rank #1
  • Estimated daily visits 2,742,801,104
  • Estimated weekly visits 18,937,637,079
  • Estimated monthly visits 82,284,033,110
  • Estimated yearly visits 987,408,397,320

Similarweb (estimates) – Traffic numbers are rough estimates, not exact analytics.

Basic info

  • HTTP status 200
  • HTML size 20 KB
  • Images on page 2
  • Title Google
  • Meta description
  • Main heading (H1)

Technical details

  • Server gws
  • X-Powered-By
  • Content-Type text/html; charset=ISO-8859-1
  • Encoding gzip
  • CSP Missing
  • HSTS Recommended

Key issues

  1. Missing source maps for large first-party JavaScript
    0/100
    Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. [Learn more about source maps](https://developer.chrome.com/docs/devtools/javascript/source-maps/).
  2. ARIA input fields do not have accessible names
    0/100
    When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. [Learn more about input field labels](https://dequeuniversity.com/rules/axe/4.11/aria-input-field-name).
  3. Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
    0/100
    Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. [Learn more about proper list structure](https://dequeuniversity.com/rules/axe/4.11/list).
  4. Render blocking requests
    0/100
    Requests are blocking the page's initial render, which may delay LCP. [Deferring or inlining](https://developer.chrome.com/docs/performance/insights/render-blocking) can move these network requests out of the critical path.
  5. Document does not have a main landmark.
    0/100
    One main landmark helps screen reader users navigate a web page. [Learn more about landmarks](https://dequeuniversity.com/rules/axe/4.11/landmark-one-main).

Page assets

  • CSS files 0
  • JS files 0
  • Images 2
  • Checked image sizes 1
  • Average size

SEO files

  • robots.txt Found (status 200)
  • Sitemap in robots.txt Present
  • sitemap.xml Found (status 200)
  • Valid XML Yes

Advanced SEO

  • Canonical URL
  • OpenGraph Missing
  • Twitter Cards Not set
  • Structured data (JSON-LD) None detected

SSL / TLS

  • Overall Secure
  • Notes Certificate looks valid.
  • Host google.com
  • Status Valid
  • Valid from Nov 24 08:38:53 2025 GMT
  • Valid to Feb 16 08:38:52 2026 GMT
  • Days remaining 60 day(s)
  • Protocol TLSv1.3 TLS 1.3
  • Cipher TLS_AES_256_GCM_SHA384 (TLSv1.3)
  • Issuer Google Trust Services
  • Subject *.google.com