Google.com.br Google
Search the world's information, including webpages, images, videos and more. Google has many special features to help you find exactly what you're loo...

google.com.br Mobile Performance
80/100
These metrics represent real-world Chrome users experience viewing google.com.br on mobile devices. Reports are focused on loading performance and other critical factors that most affect user experience. Follow our guide to track, optimize, and improve the quality of your web pages.
User Loading Experience
Cumulative Layout Shift
Largest Contentful Paint
First Contentful Paint
First Input Delay
Metrics
Total Blocking Time50/100 600 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Time to Interactive79/100 4.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Largest Contentful Paint86/100 2.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
First Contentful Paint95/100 2.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Speed Index99/100 2.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Cumulative Layout Shift100/100 0
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Should Fix (9)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Avoid multiple page redirects
Potential savings of 1,260 ms
1,260 ms
Remove unused JavaScript
Potential savings of 125 KiB
1,050 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Does not use passive listeners to improve scrolling performance
JavaScript execution time
1.0 s
Keep request counts low and transfer sizes small
30 requests • 355 KiB
Avoid chaining critical requests
1 chain found
User Timing marks and measures
2 user timings
Avoid long main-thread tasks
7 long tasks found
Largest Contentful Paint element
1 element found
Passed Audits (20)
Avoids enormous network payloads
Total size was 355 KiB
Properly size images
Preconnect to required origins
Avoids an excessive DOM size
463 elements
Remove unused CSS
All text remains visible during webfont loads
Use video formats for animated content
Eliminate render-blocking resources
Preload key requests
Minify CSS
Efficiently encode images
Minimize third-party usage
Third-party code blocked the main thread for 0 ms
Serve images in next-gen formats
Minimizes main-thread work
1.7 s
Initial server response time was short
Root document took 90 ms
Minify JavaScript
Enable text compression
Uses efficient cache policy on static assets
0 resources found
Defer offscreen images
Potential savings of 5 KiB
Avoids `document.write()`

google.com.br Mobile SEO
85/100
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more. Run these additional validators on your site to check additional SEO best practices.
Should Fix (2)
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Passed Audits (11)
Document has a `<title>` element
Document has a valid `hreflang`
Tap targets are sized appropriately
100% appropriately sized tap targets
Page isn’t blocked from indexing
Document avoids plugins
Image elements have `[alt]` attributes
Links have descriptive text
Document uses legible font sizes
100% legible text
Page has successful HTTP status code
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
robots.txt is valid

google.com.br Mobile Best Practices
85/100
These checks highlight opportunities to improve the overall code health of google.com.br mobile page. Current recommendations will help to make your page fast and secure, to create a good user experience and to avoid deprecated technologies.
Should Fix (2)
General
Browser errors were logged to the console
Trust and Safety
Does not use HTTPS
2 insecure requests found
Passed Audits (12)
Detected JavaScript libraries
Allows users to paste into password fields
Displays images with correct aspect ratio
Avoids requesting the geolocation permission on page load
Links to cross-origin destinations are safe
Serves images with appropriate resolution
Page has the HTML doctype
Avoids deprecated APIs
Avoids requesting the notification permission on page load
Avoids front-end JavaScript libraries with known security vulnerabilities
Avoids Application Cache
Properly defines charset

google.com.br Mobile Progressive Web App
46/100
These checks validate the aspects of a Progressive Web App. Learn more. These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
Should Fix (9)
PWA Optimized
Does not provide a valid `apple-touch-icon`
Does not set a theme color for the address bar.
Is not configured for a custom splash screen
Manifest doesn't have a maskable icon
Fast and reliable
`start_url` does not respond with a 200 when offline
Current page does not respond with a 200 when offline
Installable
Does not register a service worker that controls page and `start_url`
Web app manifest does not meet the installability requirements
Does not use HTTPS
2 insecure requests found
Passed Audits (5)
Page load is fast enough on mobile networks
Contains some content when JavaScript is not available
Content is sized correctly for the viewport
Redirects HTTP traffic to HTTPS
Has a `<meta name="viewport">` tag with `width` or `initial-scale`

google.com.br Mobile Accessibility
90/100
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged. These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Should Fix (3)
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
`[role]`s do not have all required `[aria-*]` attributes
Navigation
These are opportunities to improve keyboard navigation in your application.
The page does not contain a heading, skip link, or landmark region
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Passed Audits (19)
ARIA IDs are unique
Document has a `<title>` element
`[id]` attributes on active, focusable elements are unique
`<html>` element has a valid value for its `[lang]` attribute
`[aria-hidden="true"]` is not present on the document `<body>`
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
`<html>` element has a `[lang]` attribute
`[aria-hidden="true"]` elements do not contain focusable descendents
Image elements have `[alt]` attributes
`[aria-*]` attributes match their roles
No element has a `[tabindex]` value greater than 0
Links have a discernible name
`[role]` values are valid
Buttons have an accessible name
`[role]`s are contained by their required parent element
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Form elements have associated labels

Mobile Usability
100/100
These checks validate how easily a visitor can use google.com.br on a mobile device. Test results include a list of any mobile usability problems. Mobile usability problems are issues that can affect a user that visits the page on a mobile (small screen) device, including small font sizes (which are hard to read on a small screen).
Passed Audits (5)
Avoid plugins
Configure the viewport
Size content to viewport
Size tap targets appropriately
Use legible font sizes

Mobile Speed
79/100
These checks analyze the performance of google.com.br on mobile devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (1)
Avoid landing page redirects
Passed Audits (9)
Enable compression
Leverage browser caching
Reduce server response time
Minify CSS
Minify HTML
Minify JavaScript
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Optimize images
Prioritize visible content
www.google.com
www.google.net
www.google.org
www.google.info
www.google.biz
www.google.us
www.google.mobi
www.oogle.com.br
www.google.com.br
www.foogle.com.br
www.gfoogle.com.br
www.fgoogle.com.br
www.voogle.com.br
www.gvoogle.com.br
www.vgoogle.com.br
www.toogle.com.br
www.gtoogle.com.br
www.tgoogle.com.br
www.boogle.com.br
www.gboogle.com.br
www.bgoogle.com.br
www.yoogle.com.br
www.gyoogle.com.br
www.ygoogle.com.br
www.hoogle.com.br
www.ghoogle.com.br
www.hgoogle.com.br
www.gogle.com.br
www.giogle.com.br
www.goiogle.com.br
www.gioogle.com.br
www.gkogle.com.br
www.gokogle.com.br
www.gkoogle.com.br
www.glogle.com.br
www.gologle.com.br
www.gloogle.com.br
www.gpogle.com.br
www.gopogle.com.br
www.gpoogle.com.br
www.goigle.com.br
www.gooigle.com.br
www.gokgle.com.br
www.gookgle.com.br
www.golgle.com.br
www.goolgle.com.br
www.gopgle.com.br
www.goopgle.com.br
www.goole.com.br
www.goofle.com.br
www.googfle.com.br
www.goofgle.com.br
www.goovle.com.br
www.googvle.com.br
www.goovgle.com.br
www.gootle.com.br
www.googtle.com.br
www.gootgle.com.br
www.gooble.com.br
www.googble.com.br
www.goobgle.com.br
www.gooyle.com.br
www.googyle.com.br
www.gooygle.com.br
www.goohle.com.br
www.googhle.com.br
www.goohgle.com.br
www.googe.com.br
www.googpe.com.br
www.googlpe.com.br
www.googple.com.br
www.googoe.com.br
www.googloe.com.br
www.googole.com.br
www.googke.com.br
www.googlke.com.br
www.googkle.com.br
www.googl.com.br
www.googlw.com.br
www.googlew.com.br
www.googlwe.com.br
www.googls.com.br
www.googles.com.br
www.googlse.com.br
www.googld.com.br
www.googled.com.br
www.googlde.com.br
www.googlr.com.br
www.googler.com.br
www.googlre.com.br
www.google.net
www.google.org
www.google.info
www.google.biz
www.google.us
www.google.mobi
www.oogle.com.br
www.google.com.br
www.foogle.com.br
www.gfoogle.com.br
www.fgoogle.com.br
www.voogle.com.br
www.gvoogle.com.br
www.vgoogle.com.br
www.toogle.com.br
www.gtoogle.com.br
www.tgoogle.com.br
www.boogle.com.br
www.gboogle.com.br
www.bgoogle.com.br
www.yoogle.com.br
www.gyoogle.com.br
www.ygoogle.com.br
www.hoogle.com.br
www.ghoogle.com.br
www.hgoogle.com.br
www.gogle.com.br
www.giogle.com.br
www.goiogle.com.br
www.gioogle.com.br
www.gkogle.com.br
www.gokogle.com.br
www.gkoogle.com.br
www.glogle.com.br
www.gologle.com.br
www.gloogle.com.br
www.gpogle.com.br
www.gopogle.com.br
www.gpoogle.com.br
www.goigle.com.br
www.gooigle.com.br
www.gokgle.com.br
www.gookgle.com.br
www.golgle.com.br
www.goolgle.com.br
www.gopgle.com.br
www.goopgle.com.br
www.goole.com.br
www.goofle.com.br
www.googfle.com.br
www.goofgle.com.br
www.goovle.com.br
www.googvle.com.br
www.goovgle.com.br
www.gootle.com.br
www.googtle.com.br
www.gootgle.com.br
www.gooble.com.br
www.googble.com.br
www.goobgle.com.br
www.gooyle.com.br
www.googyle.com.br
www.gooygle.com.br
www.goohle.com.br
www.googhle.com.br
www.goohgle.com.br
www.googe.com.br
www.googpe.com.br
www.googlpe.com.br
www.googple.com.br
www.googoe.com.br
www.googloe.com.br
www.googole.com.br
www.googke.com.br
www.googlke.com.br
www.googkle.com.br
www.googl.com.br
www.googlw.com.br
www.googlew.com.br
www.googlwe.com.br
www.googls.com.br
www.googles.com.br
www.googlse.com.br
www.googld.com.br
www.googled.com.br
www.googlde.com.br
www.googlr.com.br
www.googler.com.br
www.googlre.com.br