Apache.org Welcome to The Apache Software Foundation!
Home page of The Apache Software Foundation
apache.org Mobile Performance
63/100
These metrics represent real-world Chrome users experience viewing apache.org 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
Largest Contentful Paint
First Contentful Paint
First Input Delay
Cumulative Layout Shift
Metrics
Total Blocking Time24/100 900 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Time to Interactive30/100 9.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Largest Contentful Paint82/100 2.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
Speed Index83/100 3.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First Contentful Paint96/100 1.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Cumulative Layout Shift100/100 0
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Should Fix (18)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Remove unused JavaScript
Potential savings of 474 KiB
4,350 ms
Serve images in next-gen formats
Potential savings of 375 KiB
1,800 ms
Efficiently encode images
Potential savings of 202 KiB
750 ms
Remove unused CSS
Potential savings of 64 KiB
600 ms
Defer offscreen images
Potential savings of 258 KiB
450 ms
Eliminate render-blocking resources
Potential savings of 150 ms
150 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
Reduce the impact of third-party code
Third-party code blocked the main thread for 1,230 ms
Ensure text remains visible during webfont load
Serve static assets with an efficient cache policy
18 resources found
Minimize main-thread work
3.8 s
Avoid an excessive DOM size
1,239 elements
Reduce JavaScript execution time
2.2 s
Avoid chaining critical requests
8 chains found
User Timing marks and measures
3 user timings
Keep request counts low and transfer sizes small
42 requests • 1,455 KiB
Avoid long main-thread tasks
9 long tasks found
Largest Contentful Paint element
1 element found
Passed Audits (11)
Avoids `document.write()`
Initial server response time was short
Root document took 90 ms
Enable text compression
Minify JavaScript
Potential savings of 4 KiB
Preconnect to required origins
Properly size images
Potential savings of 2 KiB
Avoids enormous network payloads
Total size was 1,455 KiB
Use video formats for animated content
Preload key requests
Minify CSS
Potential savings of 3 KiB
Avoid multiple page redirects
apache.org Mobile SEO
93/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 (1)
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
11% appropriately sized tap targets
Passed Audits (12)
Links have descriptive text
Document avoids plugins
Document has a valid `hreflang`
Page isn’t blocked from indexing
robots.txt is valid
Page has successful HTTP status code
Document uses legible font sizes
99.38% legible text
Links are crawlable
Document has a `<title>` element
Document has a meta description
Image elements have `[alt]` attributes
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
apache.org Mobile Best Practices
69/100
These checks highlight opportunities to improve the overall code health of apache.org 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 (4)
Trust and Safety
Does not use HTTPS
22 insecure requests found
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
General
Browser errors were logged to the console
User Experience
Serves images with low resolution
Passed Audits (10)
Detected JavaScript libraries
Avoids Application Cache
Properly defines charset
Avoids requesting the notification permission on page load
Page has the HTML doctype
Links to cross-origin destinations are safe
Allows users to paste into password fields
Displays images with correct aspect ratio
Avoids requesting the geolocation permission on page load
Avoids deprecated APIs
apache.org Mobile Progressive Web App
43/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 use HTTPS
22 insecure requests found
Does not register a service worker that controls page and `start_url`
Web app manifest does not meet the installability requirements
PWA Optimized
Manifest doesn't have a maskable icon
Does not set a theme color for the address bar.
Does not redirect HTTP traffic to HTTPS
Is not configured for a custom splash screen
Fast and reliable
Current page does not respond with a 200 when offline
`start_url` does not respond with a 200 when offline
Passed Audits (5)
Contains some content when JavaScript is not available
Content is sized correctly for the viewport
Page load is fast enough on mobile networks
Provides a valid `apple-touch-icon`
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
apache.org Mobile Accessibility
81/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 (5)
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.
`<frame>` or `<iframe>` elements do not have a title
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
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.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.
Tables and lists
These are opportunities to to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
List items (`<li>`) are not contained within `<ul>` or `<ol>` parent elements.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Passed Audits (14)
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Buttons have an accessible name
`[role]`s are contained by their required parent element
`[aria-hidden="true"]` is not present on the document `<body>`
The page contains a heading, skip link, or landmark region
`[aria-hidden="true"]` elements do not contain focusable descendents
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`<html>` element has a `[lang]` attribute
Document has a `<title>` element
`<html>` element has a valid value for its `[lang]` attribute
Image elements have `[alt]` attributes
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Links have a discernible name
Mobile Usability
80/100
These checks validate how easily a visitor can use apache.org 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).
Should Fix (1)
Size tap targets appropriately
Passed Audits (4)
Avoid plugins
Configure the viewport
Size content to viewport
Use legible font sizes
Mobile Speed
69/100
These checks analyze the performance of apache.org 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 (5)
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Leverage browser caching
Optimize images
Minify CSS
Minify JavaScript
Passed Audits (5)
Avoid landing page redirects
Enable compression
Reduce server response time
Minify HTML
Prioritize visible content
www.apache.com
www.apache.net
www.apache.org
www.apache.info
www.apache.biz
www.apache.us
www.apache.mobi
www.pache.org
www.apache.org
www.qpache.org
www.aqpache.org
www.qapache.org
www.wpache.org
www.awpache.org
www.wapache.org
www.spache.org
www.aspache.org
www.sapache.org
www.zpache.org
www.azpache.org
www.zapache.org
www.aache.org
www.aoache.org
www.apoache.org
www.aopache.org
www.alache.org
www.aplache.org
www.alpache.org
www.apche.org
www.apqche.org
www.apaqche.org
www.apqache.org
www.apwche.org
www.apawche.org
www.apwache.org
www.apsche.org
www.apasche.org
www.apsache.org
www.apzche.org
www.apazche.org
www.apzache.org
www.apahe.org
www.apaxhe.org
www.apacxhe.org
www.apaxche.org
www.apadhe.org
www.apacdhe.org
www.apadche.org
www.apafhe.org
www.apacfhe.org
www.apafche.org
www.apavhe.org
www.apacvhe.org
www.apavche.org
www.apace.org
www.apacbe.org
www.apachbe.org
www.apacbhe.org
www.apacge.org
www.apachge.org
www.apacghe.org
www.apacye.org
www.apachye.org
www.apacyhe.org
www.apacue.org
www.apachue.org
www.apacuhe.org
www.apacje.org
www.apachje.org
www.apacjhe.org
www.apacne.org
www.apachne.org
www.apacnhe.org
www.apach.org
www.apachw.org
www.apachew.org
www.apachwe.org
www.apachs.org
www.apaches.org
www.apachse.org
www.apachd.org
www.apached.org
www.apachde.org
www.apachr.org
www.apacher.org
www.apachre.org
www.apache.net
www.apache.org
www.apache.info
www.apache.biz
www.apache.us
www.apache.mobi
www.pache.org
www.apache.org
www.qpache.org
www.aqpache.org
www.qapache.org
www.wpache.org
www.awpache.org
www.wapache.org
www.spache.org
www.aspache.org
www.sapache.org
www.zpache.org
www.azpache.org
www.zapache.org
www.aache.org
www.aoache.org
www.apoache.org
www.aopache.org
www.alache.org
www.aplache.org
www.alpache.org
www.apche.org
www.apqche.org
www.apaqche.org
www.apqache.org
www.apwche.org
www.apawche.org
www.apwache.org
www.apsche.org
www.apasche.org
www.apsache.org
www.apzche.org
www.apazche.org
www.apzache.org
www.apahe.org
www.apaxhe.org
www.apacxhe.org
www.apaxche.org
www.apadhe.org
www.apacdhe.org
www.apadche.org
www.apafhe.org
www.apacfhe.org
www.apafche.org
www.apavhe.org
www.apacvhe.org
www.apavche.org
www.apace.org
www.apacbe.org
www.apachbe.org
www.apacbhe.org
www.apacge.org
www.apachge.org
www.apacghe.org
www.apacye.org
www.apachye.org
www.apacyhe.org
www.apacue.org
www.apachue.org
www.apacuhe.org
www.apacje.org
www.apachje.org
www.apacjhe.org
www.apacne.org
www.apachne.org
www.apacnhe.org
www.apach.org
www.apachw.org
www.apachew.org
www.apachwe.org
www.apachs.org
www.apaches.org
www.apachse.org
www.apachd.org
www.apached.org
www.apachde.org
www.apachr.org
www.apacher.org
www.apachre.org