Google.de 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.de Mobile Performance
78/100
These metrics represent real-world Chrome users experience viewing google.de 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
First Contentful Paint
First Input Delay
Cumulative Layout Shift
Largest Contentful Paint
Metrics
Total Blocking Time44/100 650 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Time to Interactive78/100 4.9 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 (10)
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
720 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.1 s
Minimizes main-thread work
1.7 s
Avoid long main-thread tasks
7 long tasks found
Keep request counts low and transfer sizes small
25 requests • 350 KiB
User Timing marks and measures
2 user timings
Avoid chaining critical requests
1 chain found
Largest Contentful Paint element
1 element found
Passed Audits (19)
Avoids enormous network payloads
Total size was 350 KiB
Minify JavaScript
Uses efficient cache policy on static assets
0 resources found
All text remains visible during webfont loads
Defer offscreen images
Potential savings of 5 KiB
Remove unused CSS
Enable text compression
Serve images in next-gen formats
Eliminate render-blocking resources
Avoids an excessive DOM size
463 elements
Avoids `document.write()`
Preconnect to required origins
Preload key requests
Efficiently encode images
Initial server response time was short
Root document took 100 ms
Minify CSS
Minimize third-party usage
Third-party code blocked the main thread for 0 ms
Properly size images
Use video formats for animated content
google.de 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)
Image elements have `[alt]` attributes
Document uses legible font sizes
100% legible text
Tap targets are sized appropriately
100% appropriately sized tap targets
Links have descriptive text
Document has a valid `hreflang`
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Page has successful HTTP status code
Page isn’t blocked from indexing
robots.txt is valid
Document has a `<title>` element
Document avoids plugins
google.de Mobile Best Practices
85/100
These checks highlight opportunities to improve the overall code health of google.de 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)
Avoids deprecated APIs
Properly defines charset
Avoids Application Cache
Page has the HTML doctype
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Avoids front-end JavaScript libraries with known security vulnerabilities
Detected JavaScript libraries
Allows users to paste into password fields
Displays images with correct aspect ratio
Serves images with appropriate resolution
Links to cross-origin destinations are safe
google.de 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)
Installable
Does not register a service worker that controls page and `start_url`
Does not use HTTPS
2 insecure requests found
Web app manifest does not meet the installability requirements
PWA Optimized
Does not provide a valid `apple-touch-icon`
Is not configured for a custom splash screen
Does not set a theme color for the address bar.
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
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
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Redirects HTTP traffic to HTTPS
google.de 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)
`<html>` element has a `[lang]` attribute
Image elements have `[alt]` attributes
`[aria-hidden="true"]` is not present on the document `<body>`
Buttons have an accessible name
`[id]` attributes on active, focusable elements are unique
`[role]`s are contained by their required parent element
`<html>` element has a valid value for its `[lang]` attribute
`[aria-*]` attributes have valid values
`[aria-*]` attributes match their roles
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Form elements have associated labels
ARIA IDs are unique
Links have a discernible name
No element has a `[tabindex]` value greater than 0
`[role]` values are valid
`[aria-*]` attributes are valid and not misspelled
Document has a `<title>` element
`[aria-hidden="true"]` elements do not contain focusable descendents
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Mobile Usability
100/100
These checks validate how easily a visitor can use google.de 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.de 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.de
www.google.de
www.foogle.de
www.gfoogle.de
www.fgoogle.de
www.voogle.de
www.gvoogle.de
www.vgoogle.de
www.toogle.de
www.gtoogle.de
www.tgoogle.de
www.boogle.de
www.gboogle.de
www.bgoogle.de
www.yoogle.de
www.gyoogle.de
www.ygoogle.de
www.hoogle.de
www.ghoogle.de
www.hgoogle.de
www.gogle.de
www.giogle.de
www.goiogle.de
www.gioogle.de
www.gkogle.de
www.gokogle.de
www.gkoogle.de
www.glogle.de
www.gologle.de
www.gloogle.de
www.gpogle.de
www.gopogle.de
www.gpoogle.de
www.goigle.de
www.gooigle.de
www.gokgle.de
www.gookgle.de
www.golgle.de
www.goolgle.de
www.gopgle.de
www.goopgle.de
www.goole.de
www.goofle.de
www.googfle.de
www.goofgle.de
www.goovle.de
www.googvle.de
www.goovgle.de
www.gootle.de
www.googtle.de
www.gootgle.de
www.gooble.de
www.googble.de
www.goobgle.de
www.gooyle.de
www.googyle.de
www.gooygle.de
www.goohle.de
www.googhle.de
www.goohgle.de
www.googe.de
www.googpe.de
www.googlpe.de
www.googple.de
www.googoe.de
www.googloe.de
www.googole.de
www.googke.de
www.googlke.de
www.googkle.de
www.googl.de
www.googlw.de
www.googlew.de
www.googlwe.de
www.googls.de
www.googles.de
www.googlse.de
www.googld.de
www.googled.de
www.googlde.de
www.googlr.de
www.googler.de
www.googlre.de
www.google.net
www.google.org
www.google.info
www.google.biz
www.google.us
www.google.mobi
www.oogle.de
www.google.de
www.foogle.de
www.gfoogle.de
www.fgoogle.de
www.voogle.de
www.gvoogle.de
www.vgoogle.de
www.toogle.de
www.gtoogle.de
www.tgoogle.de
www.boogle.de
www.gboogle.de
www.bgoogle.de
www.yoogle.de
www.gyoogle.de
www.ygoogle.de
www.hoogle.de
www.ghoogle.de
www.hgoogle.de
www.gogle.de
www.giogle.de
www.goiogle.de
www.gioogle.de
www.gkogle.de
www.gokogle.de
www.gkoogle.de
www.glogle.de
www.gologle.de
www.gloogle.de
www.gpogle.de
www.gopogle.de
www.gpoogle.de
www.goigle.de
www.gooigle.de
www.gokgle.de
www.gookgle.de
www.golgle.de
www.goolgle.de
www.gopgle.de
www.goopgle.de
www.goole.de
www.goofle.de
www.googfle.de
www.goofgle.de
www.goovle.de
www.googvle.de
www.goovgle.de
www.gootle.de
www.googtle.de
www.gootgle.de
www.gooble.de
www.googble.de
www.goobgle.de
www.gooyle.de
www.googyle.de
www.gooygle.de
www.goohle.de
www.googhle.de
www.goohgle.de
www.googe.de
www.googpe.de
www.googlpe.de
www.googple.de
www.googoe.de
www.googloe.de
www.googole.de
www.googke.de
www.googlke.de
www.googkle.de
www.googl.de
www.googlw.de
www.googlew.de
www.googlwe.de
www.googls.de
www.googles.de
www.googlse.de
www.googld.de
www.googled.de
www.googlde.de
www.googlr.de
www.googler.de
www.googlre.de