En.wikisource.org Site Title
Wikisource, the free library
En.wikisource.org Test Results
En.wikisource.org Mobile Performance: 86/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Defer offscreen images
Potential savings of 200 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Avoid multiple page redirects
Potential savings of 1,290 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Serve images in next-gen formats
Potential savings of 118 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Largest Contentful Paint element
3,390 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Serve static assets with an efficient cache policy
22 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Reduce unused JavaScript
Potential savings of 93 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Reduce unused CSS
Potential savings of 54 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 0 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 how to use modern JavaScript
Does not use 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 about adopting passive event listeners.
Time to Interactive
4.8 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.
Max Potential First Input Delay
140 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.
First Meaningful Paint
2.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
En.wikisource.org Mobile SEO: 85/100
Quick overview:
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.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
En.wikisource.org Mobile Best Practices: 76/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.
Browser errors were 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 about this errors in console diagnostic audit
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.
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.
En.wikisource.org Mobile Accessibility: 88/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.
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.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
`<dl>`'s do not contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Similar sites
Similar tests
www.en.com
www.en.net
www.en.org
www.en.info
www.en.biz
www.en.us
www.en.mobi
www.n.wikisource.org
www.en.wikisource.org
www.wn.wikisource.org
www.ewn.wikisource.org
www.wen.wikisource.org
www.sn.wikisource.org
www.esn.wikisource.org
www.sen.wikisource.org
www.dn.wikisource.org
www.edn.wikisource.org
www.den.wikisource.org
www.rn.wikisource.org
www.ern.wikisource.org
www.ren.wikisource.org
www.e.wikisource.org
www.eb.wikisource.org
www.enb.wikisource.org
www.ebn.wikisource.org
www.eh.wikisource.org
www.enh.wikisource.org
www.ehn.wikisource.org
www.ej.wikisource.org
www.enj.wikisource.org
www.ejn.wikisource.org
www.em.wikisource.org
www.enm.wikisource.org
www.emn.wikisource.org
www.en.net
www.en.org
www.en.info
www.en.biz
www.en.us
www.en.mobi
www.n.wikisource.org
www.en.wikisource.org
www.wn.wikisource.org
www.ewn.wikisource.org
www.wen.wikisource.org
www.sn.wikisource.org
www.esn.wikisource.org
www.sen.wikisource.org
www.dn.wikisource.org
www.edn.wikisource.org
www.den.wikisource.org
www.rn.wikisource.org
www.ern.wikisource.org
www.ren.wikisource.org
www.e.wikisource.org
www.eb.wikisource.org
www.enb.wikisource.org
www.ebn.wikisource.org
www.eh.wikisource.org
www.enh.wikisource.org
www.ehn.wikisource.org
www.ej.wikisource.org
www.enj.wikisource.org
www.ejn.wikisource.org
www.em.wikisource.org
www.enm.wikisource.org
www.emn.wikisource.org