Website performance of https://google.com

Generated on September 10, 2024 at 3:23 PM from Iowa, US

There were issues affecting this run of Lighthouse:

  • The page may not be loading as expected because your test URL (https://google.com/) was redirected to https://www.google.com/. Try testing the second URL directly.
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
Metrics
First Contentful Paint
0.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Time to Interactive
0.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Speed Index
0.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Largest Contentful Paint
0.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Cumulative Layout Shift
0.007
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Show audits relevant to:
Diagnostics
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.FCPLCP
URL
Potential Savings
…v58/4UaRrENHs….woff2
(fonts.gstatic.com)
30 ms
…v18/KFOmCnqEu….woff2
(fonts.gstatic.com)
40 ms
Image elements do not have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn moreCLS
URL
div.KxwPGc > div.KxwPGc > a.pHiOh > img.Pb9hCb
<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABUAAAAYCAMAAAAiV0Z6AAAAPFBM…" class="Pb9hCb" alt="" data-csiid="cmTgZoTIHo7B0PEPlIK2mQ4_11" data-atf="1">
Does not have a <meta name="viewport"> tag with width or initial-scale
No `<meta name="viewport">` tag found
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more.TBT
Minimize main-thread work 4.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn moreTBT
Category
Time Spent
Other
3,995 ms
Script Evaluation
0 ms
Avoid chaining critical requests 2 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.FCPLCP
Maximum critical path latency: 910 ms
Initial Navigation
- 10 ms, 2.75 KiB
Keep request counts low and transfer sizes small 40 requests • 962 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Resource Type
Requests
Transfer Size
Total
40
962.4 KiB
Script
12
799.6 KiB
Document
2
73.6 KiB
Font
2
62.2 KiB
Other
17
12.7 KiB
Image
5
9.5 KiB
Stylesheet
2
4.8 KiB
Media
0
0.0 KiB
Third-party
11
316.5 KiB
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport. Learn MoreLCP
Element
Google
<img class="lnXdpd" alt="Google" height="92" src="https://www.google.com/images/branding/googlelogo/1x/googlelogo_color_272x…" srcset="/images/branding/googlelogo/1x/googlelogo_color_272x92dp.png 1x, /images/b…" width="272" data-csiid="cmTgZoTIHo7B0PEPlIK2mQ4_1" data-atf="1">
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (33)
Show Hide
Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.FCPLCP
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.FCPLCP
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.FCPLCP
Reduce unused CSS Potential savings of 15 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn more.FCPLCP
URL
Transfer Size
Potential Savings
h1,ol,ul,li,button{margin:0;padding:0} ...
15.9 KiB
14.7 KiB
Reduce unused JavaScript Potential savings of 398 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn more.LCP
URL
Transfer Size
Potential Savings
344.9 KiB
159.0 KiB
151.6 KiB
90.1 KiB
93.6 KiB
53.0 KiB
…ed=1/rs=AA2YrTsOt…
(www.gstatic.com)
78.7 KiB
45.3 KiB
42.3 KiB
26.3 KiB
69.2 KiB
24.5 KiB
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.
Serve images in next-gen formats
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.FCPLCP
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.FCPLCP
Initial server response time was short Root document took 270 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.FCPLCP
URL
Time Spent
270 ms
Avoid multiple page redirects Potential savings of 200 ms
Redirects introduce additional delays before the page can be loaded. Learn more.FCPLCP
URL
Time Spent
200 ms
0 ms
Preload key requests
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.FCPLCP
Use HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn moreLCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. TBT
Avoid serving legacy JavaScript to modern browsers Potential savings of 7 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn MoreTBT
URL
Potential Savings
7.4 KiB
Date.prototype.toISOString
Preload Largest Contentful Paint image
Preload the image used by the LCP element in order to improve your LCP time. Learn more.LCP
URL
Potential Savings
Google
<img class="lnXdpd" alt="Google" height="92" src="https://www.google.com/images/branding/googlelogo/1x/googlelogo_color_272x…" srcset="/images/branding/googlelogo/1x/googlelogo_color_272x92dp.png 1x, /images/b…" width="272" data-csiid="cmTgZoTIHo7B0PEPlIK2mQ4_1" data-atf="1">
0 ms
Avoids enormous network payloads Total size was 962 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.LCP
URL
Transfer Size
344.9 KiB
151.6 KiB
93.6 KiB
…ed=1/rs=AA2YrTsOt…
(www.gstatic.com)
78.7 KiB
69.2 KiB
60.8 KiB
…v58/4UaRrENHs….woff2
(fonts.gstatic.com)
51.6 KiB
42.3 KiB
/widget/callout?prid=…
(ogs.google.com)
12.9 KiB
…v18/KFOmCnqEu….woff2
(fonts.gstatic.com)
10.6 KiB
Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoids an excessive DOM size 355 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.TBT
Statistic
Element
Value
Total DOM Elements
355
Maximum DOM Depth
div.iOHNLb > span.z1asCe > svg > rect
<rect fill="none" height="24" width="24">
18
Maximum Child Elements
#shJ2Vb{display:none}.OBMEnb{padding:0;margin:0}.G43f7e{display:flex;flex-direc…
<div jsname="aajZCb" class="aajZCb">
16
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
JavaScript execution time 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
Unattributable
3,995 ms
0 ms
0 ms
Minimize third-party usage Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
254 KiB
0 ms
94 KiB
0 ms
…ed=1/rs=AA2YrTsOt…
(www.gstatic.com)
79 KiB
0 ms
69 KiB
0 ms
62 KiB
0 ms
…v58/4UaRrENHs….woff2
(fonts.gstatic.com)
52 KiB
0 ms
…v18/KFOmCnqEu….woff2
(fonts.gstatic.com)
11 KiB
0 ms
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more.
Element
Google
<img class="lnXdpd" alt="Google" height="92" src="https://www.google.com/images/branding/googlelogo/1x/googlelogo_color_272x…" srcset="/images/branding/googlelogo/1x/googlelogo_color_272x92dp.png 1x, /images/b…" width="272" data-csiid="cmTgZoTIHo7B0PEPlIK2mQ4_1" data-atf="1">
Avoid large layout shifts
These DOM elements contribute most to the CLS of the page.CLS
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
Avoids document.write()
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.
Avoid long main-thread tasks
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn moreTBT
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn moreCLS
Avoids unload event listeners
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more
General
Issues were logged in the Issues panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Issue type
SameSite cookie
/gen_204?s=…
(www.google.com)
/gen_204?atyp=…
(www.google.com)
/widget/callout?prid=…
(ogs.google.com)
/gen_204?atyp=…
(www.google.com)
/gen_204?atyp=…
(www.google.com)
/async/hpba?vet=…
(www.google.com)
/gen_204?atyp=…
(www.google.com)
/gen_204?atyp=…
(www.google.com)
/gen_204?atyp=…
(www.google.com)
/robots.txt
(www.google.com)
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more.
Name
Version
Boq
Wiz
Missing source maps for large first-party JavaScript
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.
URL
Map URL
Large JavaScript file is missing a source map
Large JavaScript file is missing a source map
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn more
Description
Directive
Severity
No CSP found in enforcement mode
High
Passed audits (11)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more.
Avoids front-end JavaScript libraries with known security vulnerabilities
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Allows users to paste into password fields
Preventing password pasting undermines good security policy. Learn more.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more.
Properly defines charset
A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more.
No browser errors logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more
Not applicable (1)
Show Hide
Fonts with font-display: optional are preloaded
Preload `optional` fonts so first-time visitors may use them. Learn more
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more.
Mobile Friendly
Does not have a <meta name="viewport"> tag with width or initial-scale
No `<meta name="viewport">` tag found
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more.TBT
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Content Best Practices
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
Format your HTML in a way that enables crawlers to better understand your app’s content.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more.
Run these additional validators on your site to check additional SEO best practices.
Passed audits (9)
Show Hide
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more.
Links are crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more.
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more.
Document avoids plugins
Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more.
Not applicable (3)
Show Hide
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more.
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more.
Tap targets are sized appropriately
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.
  • Captured at Sep 10, 2024, 3:23 PM UTC
  • Emulated Desktop with Lighthouse 9.4.0
    CPU/Memory Power: 1107 CPU throttling: 1x slowdown (Simulated) Axe version: 4.3.5
  • Single page load
    This data is taken from a single page load, as opposed to field data summarizing many sessions.
  • Initial page load
  • Custom throttling
    Network throttling: 0 ms TCP RTT, 50,000 Kbps throughput (Simulated)
  • Using HeadlessChromium 93.0.4577.82 with cli
    User agent (network): "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4695.0 Safari/537.36 Chrome-Lighthouse"
Generated by Lighthouse 9.4.0 | File an issue