Pr24.us Site Title

pr24.us - pr24.us

Pr24.us Meta Description

pr24.us

Pr24.us Test Results

Pr24.us Mobile Performance: 96/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid multiple page redirects
Potential savings of 1,400 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Largest Contentful Paint element
2,510 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn how to avoid document.write().
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

Pr24.us Mobile SEO: 50/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.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Page is blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Pr24.us Mobile Best Practices: 76/100
Quick overview:
General
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.
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration. Document must contain a doctype
Pr24.us Mobile Accessibility: 82/100
Quick overview:
Contrast
These are opportunities to improve the legibility of your content.
Links rely on color to be distinguishable.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Best practices
These items highlight common accessibility best practices.
The document uses `<meta http-equiv="refresh">`
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
Similar tests
www.pr24.com
www.pr24.net
www.pr24.org
www.pr24.info
www.pr24.biz
www.pr24.us
www.pr24.mobi
www.r24.us
www.pr24.us
www.or24.us
www.por24.us
www.opr24.us
www.lr24.us
www.plr24.us
www.lpr24.us
www.p24.us
www.pe24.us
www.pre24.us
www.per24.us
www.pd24.us
www.prd24.us
www.pdr24.us
www.pf24.us
www.prf24.us
www.pfr24.us
www.pt24.us
www.prt24.us
www.ptr24.us
www.pr4.us
www.pr2.us
Last Tested: