De.wikipedia.org Test Results

De.wikipedia.org Mobile Performance: 61/100
Quick overview:
Avoid large layout shifts
2 elements found
These DOM elements were most affected by layout shifts. Some layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Time to Interactive
6.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
First Meaningful Paint
3.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Max Potential First Input Delay
150 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

De.wikipedia.org Mobile SEO: 90/100
Quick overview:
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 how to make pages mobile-friendly.
Tap targets are not sized appropriately
69% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.
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
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

De.wikipedia.org Mobile Best Practices: 78/100
Quick overview:
General
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 about source maps.
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Trust and Safety
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 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 about HTTPS.
De.wikipedia.org Mobile PWA: 75/100
Quick overview:
PWA Optimized
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 about splash screens. Failures: Manifest does not have a PNG icon of at least 512px.
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 about maskable manifest icons.
De.wikipedia.org Mobile Accessibility: 91/100
Quick overview:
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.
Values assigned to `role=""` are not valid ARIA roles.
ARIA `role`s enable assistive technologies to know the role of each element on the web page. If the `role` values are misspelled, not existing ARIA `role` values, or abstract roles, then the purpose of the element will not be communicated to users of assistive technologies. Learn more about ARIA roles.
`[aria-hidden="true"]` elements contain focusable descendents
Focusable descendents within an `aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [Learn how `aria-hidden` affects focusable elements.
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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Similar sites
Similar tests
www.de.com
www.de.net
www.de.org
www.de.info
www.de.biz
www.de.us
www.de.mobi
www.e.wikipedia.org
www.de.wikipedia.org
www.xe.wikipedia.org
www.dxe.wikipedia.org
www.xde.wikipedia.org
www.se.wikipedia.org
www.dse.wikipedia.org
www.sde.wikipedia.org
www.ee.wikipedia.org
www.dee.wikipedia.org
www.ede.wikipedia.org
www.re.wikipedia.org
www.dre.wikipedia.org
www.rde.wikipedia.org
www.fe.wikipedia.org
www.dfe.wikipedia.org
www.fde.wikipedia.org
www.ce.wikipedia.org
www.dce.wikipedia.org
www.cde.wikipedia.org
www.d.wikipedia.org
www.dw.wikipedia.org
www.dew.wikipedia.org
www.dwe.wikipedia.org
www.ds.wikipedia.org
www.des.wikipedia.org
www.dd.wikipedia.org
www.ded.wikipedia.org
www.dde.wikipedia.org
www.dr.wikipedia.org
www.der.wikipedia.org
Last Tested: