Leo.org Site Title
LEO.org - Ihr Sprachangebot im Web
Leo.org Meta Description
LEO.org: Ihr Sprachexperte im Internet - mit Online-Wörterbüchern, Forum, Vokabeltrainer und Sprachkursen. Natürlich auch als App.
Leo.org Test Results
Leo.org Mobile Performance: 36/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Preload key requests. Potential savings of 3,930 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.
Avoid multiple page redirects. Potential savings of 2,190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Remove unused JavaScript. Potential savings of 100 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Serve images in next-gen formats. Potential savings of 80 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Eliminate render-blocking resources. Potential savings of 170 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Remove unused CSS. Potential savings of 24 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Defer offscreen images. Potential savings of 88 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Efficiently encode images. Potential savings of 50 KiB
Optimized images load faster and consume less cellular data. Learn more.
Reduce initial server response time. Root document took 660 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.
Minimize main-thread work
3.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Reduce JavaScript execution time
1.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Keep request counts low and transfer sizes small
51 requests • 692 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid long main-thread tasks
11 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Avoid chaining critical requests
3 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.
Leo.org Mobile SEO: 90/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
1 link found
Descriptive link text helps search engines understand your content. Learn more.
Mobile Friendly
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.
Tap targets are not sized appropriately
68% appropriately sized tap targets
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.
Leo.org Mobile Best Practices: 69/100
Quick overview:
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.
Trust and Safety
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
Does not use HTTPS
1 insecure request found
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 servedover 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.
Leo.org Mobile Progressive Web App: 54/100
Quick overview:
Fast and reliable
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. The start_url did respond, but not via a service worker.
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
PWA Optimized
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more.
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: Manifest does not have `name`.
Installable
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: Manifest's `display` value is not one of: minimal-ui | fullscreen | standalone,
Manifest does not have `short_name`,
Manifest does not have `name`.
Does not use HTTPS
1 insecure request found
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 servedover 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.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Leo.org Mobile Accessibility: 88/100
Quick overview:
Navigation
These are opportunities to improve keyboard navigation in your application.
Some elements have a `[tabindex]` value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn more.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Similar sites
Similar tests
www.leo.com
www.leo.net
www.leo.org
www.leo.info
www.leo.biz
www.leo.us
www.leo.mobi
www.eo.org
www.leo.org
www.peo.org
www.lpeo.org
www.pleo.org
www.oeo.org
www.loeo.org
www.oleo.org
www.keo.org
www.lkeo.org
www.kleo.org
www.lo.org
www.lwo.org
www.lewo.org
www.lweo.org
www.lso.org
www.leso.org
www.lseo.org
www.ldo.org
www.ledo.org
www.ldeo.org
www.lro.org
www.lero.org
www.lreo.org
www.le.org
www.lei.org
www.leoi.org
www.leio.org
www.lek.org
www.leok.org
www.leko.org
www.lel.org
www.leol.org
www.lelo.org
www.lep.org
www.leop.org
www.lepo.org
www.leo.net
www.leo.org
www.leo.info
www.leo.biz
www.leo.us
www.leo.mobi
www.eo.org
www.leo.org
www.peo.org
www.lpeo.org
www.pleo.org
www.oeo.org
www.loeo.org
www.oleo.org
www.keo.org
www.lkeo.org
www.kleo.org
www.lo.org
www.lwo.org
www.lewo.org
www.lweo.org
www.lso.org
www.leso.org
www.lseo.org
www.ldo.org
www.ledo.org
www.ldeo.org
www.lro.org
www.lero.org
www.lreo.org
www.le.org
www.lei.org
www.leoi.org
www.leio.org
www.lek.org
www.leok.org
www.leko.org
www.lel.org
www.leol.org
www.lelo.org
www.lep.org
www.leop.org
www.lepo.org