Pgttp.com Test Results

Pgttp.com Mobile Performance: 98/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Eliminate render-blocking resources
Potential savings of 390 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Avoid multiple page redirects
Potential savings of 1,080 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Serve static assets with an efficient cache policy
8 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 46 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.

Pgttp.com Mobile SEO: 91/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.

Pgttp.com Mobile Best Practices: 76/100
Quick overview:
User Experience
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Document doesn't use legible font sizes
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. Text is illegible because there's no viewport meta tag optimized for mobile screens.
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.
Pgttp.com Mobile Accessibility: 96/100
Quick overview:
Best practices
These items highlight common accessibility best practices.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Similar tests
www.pgttp.com
www.pgttp.net
www.pgttp.org
www.pgttp.info
www.pgttp.biz
www.pgttp.us
www.pgttp.mobi
www.gttp.com
www.pgttp.com
www.ogttp.com
www.pogttp.com
www.opgttp.com
www.lgttp.com
www.plgttp.com
www.lpgttp.com
www.pttp.com
www.pfttp.com
www.pgfttp.com
www.pfgttp.com
www.pvttp.com
www.pgvttp.com
www.pvgttp.com
www.ptttp.com
www.pgtttp.com
www.ptgttp.com
www.pbttp.com
www.pgbttp.com
www.pbgttp.com
www.pyttp.com
www.pgyttp.com
www.pygttp.com
www.phttp.com
www.pghttp.com
www.phgttp.com
www.pgtp.com
www.pgrtp.com
www.pgtrtp.com
www.pgrttp.com
www.pgftp.com
www.pgtftp.com
www.pggtp.com
www.pgtgtp.com
www.pggttp.com
www.pgytp.com
www.pgtytp.com
www.pgtrp.com
www.pgttrp.com
www.pgtfp.com
www.pgttfp.com
www.pgtgp.com
www.pgttgp.com
www.pgtyp.com
www.pgttyp.com
www.pgtt.com
www.pgtto.com
www.pgttpo.com
www.pgttop.com
www.pgttl.com
www.pgttpl.com
www.pgttlp.com
www.pgttp.con
Last Tested: