Pmg.su Test Results
Pmg.su Mobile Performance: 25/100
Quick overview:
Max Potential First Input Delay
1,180 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.
Time to Interactive
34.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.
First Meaningful Paint
6.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Network Round Trip Times
40 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.
Tasks
Lists the toplevel main thread tasks that executed during page load.
Metrics
Collects all available metrics.
Server Backend Latencies
290 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.
Final Screenshot
The last screenshot captured of the pageload.
1421767177038
Network Requests
Lists the network requests that were made during page load.
Script Treemap Data
Used for treemap app
Diagnostics
Collection of useful page vitals.
Pmg.su Mobile SEO: 93/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Pmg.su Mobile Best Practices: 41/100
Quick overview:
General
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Registers an `unload` listener
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more about unload event listeners
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
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.
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
Pmg.su Mobile PWA: 75/100
Quick overview:
PWA Optimized
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: Manifest does not have a PNG icon of at least 512px,
Manifest does not have `name`.
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.
Pmg.su Mobile Accessibility: 81/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.
`button`, `link`, and `menuitem` elements do not have accessible names.
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
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.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
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.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Touch targets have sufficient size and 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.
Identical links have the same purpose.
Links with the same destination should have the same description, to help users understand the link's purpose and decide whether to follow it. Learn more about identical links.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Similar sites
Similar tests
www.pmg.com
www.pmg.net
www.pmg.org
www.pmg.info
www.pmg.biz
www.pmg.us
www.pmg.mobi
www.mg.su
www.pmg.su
www.omg.su
www.pomg.su
www.opmg.su
www.lmg.su
www.plmg.su
www.lpmg.su
www.pg.su
www.png.su
www.pmng.su
www.pnmg.su
www.pjg.su
www.pmjg.su
www.pjmg.su
www.pkg.su
www.pmkg.su
www.pkmg.su
www.pm.su
www.pmf.su
www.pmgf.su
www.pmfg.su
www.pmv.su
www.pmgv.su
www.pmvg.su
www.pmt.su
www.pmgt.su
www.pmtg.su
www.pmb.su
www.pmgb.su
www.pmbg.su
www.pmy.su
www.pmgy.su
www.pmyg.su
www.pmh.su
www.pmgh.su
www.pmhg.su
www.pmg.net
www.pmg.org
www.pmg.info
www.pmg.biz
www.pmg.us
www.pmg.mobi
www.mg.su
www.pmg.su
www.omg.su
www.pomg.su
www.opmg.su
www.lmg.su
www.plmg.su
www.lpmg.su
www.pg.su
www.png.su
www.pmng.su
www.pnmg.su
www.pjg.su
www.pmjg.su
www.pjmg.su
www.pkg.su
www.pmkg.su
www.pkmg.su
www.pm.su
www.pmf.su
www.pmgf.su
www.pmfg.su
www.pmv.su
www.pmgv.su
www.pmvg.su
www.pmt.su
www.pmgt.su
www.pmtg.su
www.pmb.su
www.pmgb.su
www.pmbg.su
www.pmy.su
www.pmgy.su
www.pmyg.su
www.pmh.su
www.pmgh.su
www.pmhg.su