Power.org Test Results

Power.org Mobile Performance: 77/100
Quick overview:
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.
Time to Interactive
3.3 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.
Diagnostics
Collection of useful page vitals.
Metrics
Collects all available metrics.
Network Requests
Lists the network requests that were made during page load.
Final Screenshot
The last screenshot captured of the pageload.

3302116826710

Server Backend Latencies
30 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
Tasks
Lists the toplevel main thread tasks that executed during page load.
Network Round Trip Times
20 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.
Script Treemap Data
Used for treemap app

Power.org Mobile SEO: 83/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.
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.
Document doesn't use legible font sizes
0% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.

Power.org Mobile Best Practices: 77/100
Quick overview:
General
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection 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.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Power.org Mobile PWA: 38/100
Quick overview:
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 about maskable manifest icons. No manifest was fetched
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more about theming the address bar. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
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: No manifest was fetched.
Installable
Web app manifest or service worker do not meet the installability requirements
1 reason
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. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more about manifest installability requirements.
Power.org Mobile Accessibility: 88/100
Quick overview:
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Document has a main landmark.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Navigation
These are opportunities to improve keyboard navigation in your application.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
Similar sites
Similar tests
www.power.com
www.power.net
www.power.org
www.power.info
www.power.biz
www.power.us
www.power.mobi
www.ower.org
www.power.org
www.oower.org
www.poower.org
www.opower.org
www.lower.org
www.plower.org
www.lpower.org
www.pwer.org
www.piwer.org
www.poiwer.org
www.piower.org
www.pkwer.org
www.pokwer.org
www.pkower.org
www.plwer.org
www.polwer.org
www.ppwer.org
www.popwer.org
www.ppower.org
www.poer.org
www.poqer.org
www.powqer.org
www.poqwer.org
www.poaer.org
www.powaer.org
www.poawer.org
www.poser.org
www.powser.org
www.poswer.org
www.poeer.org
www.poweer.org
www.poewer.org
www.powr.org
www.powwr.org
www.powewr.org
www.powwer.org
www.powsr.org
www.powesr.org
www.powdr.org
www.powedr.org
www.powder.org
www.powrr.org
www.powerr.org
www.powrer.org
www.powe.org
www.powee.org
www.powere.org
www.powed.org
www.powerd.org
www.powef.org
www.powerf.org
www.powefr.org
www.powet.org
www.powert.org
www.powetr.org
Last Tested: