H-p-n.fr Site Title

HPN Propreté, services de nettoyage professionnels

H-p-n.fr Meta Description

HPN Propreté propose des services de nettoyage pour les entreprises, les industriels, les collectivités et les particuliers, dans l'Aisne, l'Oise, la Marne et l'Île de France.

H-p-n.fr Test Results

H-p-n.fr Mobile Performance: 78/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Eliminate render-blocking resources. Potential savings of 2,730 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.
Enable text compression. Potential savings of 235 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
Remove unused JavaScript. Potential savings of 235 KB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Serve images in next-gen formats. Potential savings of 186 KB
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.
Minify JavaScript. Potential savings of 103 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.
Minify CSS. Potential savings of 3 KB
Minifying CSS files can reduce network payload sizes. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Serve static assets with an efficient cache policy
15 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Keep request counts low and transfer sizes small
17 requests • 579 KB
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 element that was identified as the Largest Contentful Paint. Learn More
Avoid large layout shifts
No elements found
These DOM elements contribute most to the CLS of the page.
Avoid chaining critical requests
6 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.

H-p-n.fr Mobile SEO: 64/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
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 more.
Tap targets are not sized appropriately
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. Tap targets are too small because there's no viewport meta tag optimized for mobile screens
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more. 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. Text is illegible because there's no viewport meta tag optimized for mobile screens.

H-p-n.fr Mobile Best Practices: 62/100
Quick overview:
Trust and Safety
Includes front-end JavaScript libraries with known security vulnerabilities
6 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
17 insecure requests 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 servedover 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.
User Experience
Displays images with inappropriate size
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.
Browser Compatibility
Charset declaration is missing or occurs too late in the HTML
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more.
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more. Expected publicId to be an empty string
H-p-n.fr Mobile Progressive Web App: 29/100
Quick overview:
PWA Optimized
Does not redirect HTTP traffic to HTTPS
If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more. No `<meta name="viewport">` tag found
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. No manifest was fetched
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
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: No manifest was fetched.
Content is not sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more. The viewport size of 980px does not match the window size of 360px.
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Installable
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.
Does not use HTTPS
17 insecure requests 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 servedover 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.
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
Fast and reliable
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
H-p-n.fr Mobile Accessibility: 63/100
Quick overview:
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.
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.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. 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.
Similar tests
www.h-p-n.com
www.h-p-n.net
www.h-p-n.org
www.h-p-n.info
www.h-p-n.biz
www.h-p-n.us
www.h-p-n.mobi
www.-p-n.fr
www.h-p-n.fr
www.b-p-n.fr
www.hb-p-n.fr
www.bh-p-n.fr
www.g-p-n.fr
www.hg-p-n.fr
www.gh-p-n.fr
www.y-p-n.fr
www.hy-p-n.fr
www.yh-p-n.fr
www.u-p-n.fr
www.hu-p-n.fr
www.uh-p-n.fr
www.j-p-n.fr
www.hj-p-n.fr
www.jh-p-n.fr
www.n-p-n.fr
www.hn-p-n.fr
www.nh-p-n.fr
www.hp-n.fr
www.h--n.fr
www.h-o-n.fr
www.h-po-n.fr
www.h-op-n.fr
www.h-l-n.fr
www.h-pl-n.fr
www.h-lp-n.fr
www.h-pn.fr
www.h-p-.fr
www.h-p-b.fr
www.h-p-nb.fr
www.h-p-bn.fr
www.h-p-h.fr
www.h-p-nh.fr
www.h-p-hn.fr
www.h-p-j.fr
www.h-p-nj.fr
www.h-p-jn.fr
www.h-p-m.fr
www.h-p-nm.fr
www.h-p-mn.fr
Last Tested: