Ap3.ee Test Results
Ap3.ee Mobile Performance: 17/100
Quick overview:
Max Potential First Input Delay
5,190 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
24.6 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
4.8 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
10 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.
Server Backend Latencies
150 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.
Script Treemap Data
Used for treemap app
Final Screenshot
The last screenshot captured of the pageload.
313626454440
Tasks
Lists the toplevel main thread tasks that executed during page load.
Metrics
Collects all available metrics.
Diagnostics
Collection of useful page vitals.
Network Requests
Lists the network requests that were made during page load.
Ap3.ee Mobile SEO: 90/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
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.
Tap targets are not sized appropriately
80% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.
Ap3.ee Mobile Best Practices: 73/100
Quick overview:
General
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
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
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
Ap3.ee Mobile PWA: 100/100
Quick overview:
Ap3.ee Mobile Accessibility: 79/100
Quick overview:
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
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.
Values assigned to `role=""` are not valid ARIA roles.
ARIA `role`s enable assistive technologies to know the role of each element on the web page. If the `role` values are misspelled, not existing ARIA `role` values, or abstract roles, then the purpose of the element will not be communicated to users of assistive technologies. Learn more about ARIA roles.
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.
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.
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.
`<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.
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.
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.
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.
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.
Similar sites
Similar tests
www.ap3.com
www.ap3.net
www.ap3.org
www.ap3.info
www.ap3.biz
www.ap3.us
www.ap3.mobi
www.p3.ee
www.ap3.ee
www.qp3.ee
www.aqp3.ee
www.qap3.ee
www.wp3.ee
www.awp3.ee
www.wap3.ee
www.sp3.ee
www.asp3.ee
www.sap3.ee
www.zp3.ee
www.azp3.ee
www.zap3.ee
www.a3.ee
www.ao3.ee
www.apo3.ee
www.aop3.ee
www.al3.ee
www.apl3.ee
www.alp3.ee
www.ap.ee
www.ap3.net
www.ap3.org
www.ap3.info
www.ap3.biz
www.ap3.us
www.ap3.mobi
www.p3.ee
www.ap3.ee
www.qp3.ee
www.aqp3.ee
www.qap3.ee
www.wp3.ee
www.awp3.ee
www.wap3.ee
www.sp3.ee
www.asp3.ee
www.sap3.ee
www.zp3.ee
www.azp3.ee
www.zap3.ee
www.a3.ee
www.ao3.ee
www.apo3.ee
www.aop3.ee
www.al3.ee
www.apl3.ee
www.alp3.ee
www.ap.ee