Bp4x.xyz Test Results
Bp4x.xyz Mobile Performance: 77/100
These suggestions can help your page load faster. They don't directly affect the Performance score.
Serve images in next-gen formats. Potential savings of 3,260 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Eliminate render-blocking resources. Potential savings of 770 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Efficiently encode images. Potential savings of 154 KiB
Optimized images load faster and consume less cellular data. Learn more.
Remove unused CSS. Potential savings of 34 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
More information about the performance of your application. These numbers don't directly affect the Performance score.
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.
Serve static assets with an efficient cache policy
19 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
Avoid enormous network payloads
Total size was 4,754 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Avoid an excessive DOM size
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Keep request counts low and transfer sizes small
41 requests • 4,754 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid chaining critical requests
15 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Avoid large layout shifts
1 element found
These DOM elements contribute most to the CLS of the page.
Avoid long main-thread tasks
3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Bp4x.xyz Mobile SEO: 99/100
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Tap targets are not sized appropriately
95% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.
Bp4x.xyz Mobile Best Practices: 73/100
Trust and Safety
3 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
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.
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
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.
Bp4x.xyz Mobile Progressive Web App: 67/100
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: Manifest does not have `theme_color`, No `<meta name="theme-color">` tag found.
Does not register a service worker that controls page and `start_url`
The 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. Learn more.
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 more.
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. Failures: Manifest does not have a PNG icon of at least 512px, Manifest does not have `background_color`, Manifest does not have `theme_color`.
Bp4x.xyz Mobile Accessibility: 81/100
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.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
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 more.
These are opportunities to improve keyboard navigation in your application.
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.
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.
These are opportunities to improve the legibility of your content.