5.5 sec in total
174 ms
5 sec
343 ms
Welcome to planit.fr homepage info - get ready to check Planit best content right away, or after learning these important things about planit.fr
Découvrez qui nous sommes, ce que nous faisons et l’histoire de notre marque.
Visit planit.frWe analyzed Planit.fr page load time and found that the first response time was 174 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
planit.fr performance score
name
value
score
weighting
Value14.2 s
0/100
10%
Value24.1 s
0/100
25%
Value27.8 s
0/100
10%
Value10,990 ms
0/100
30%
Value0.238
52/100
15%
Value33.2 s
0/100
10%
174 ms
1984 ms
196 ms
44 ms
56 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Planit.fr, 29% (22 requests) were made to Hexagon.blob.core.windows.net and 11% (8 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Hexagonmi.com.
Page size can be reduced by 2.5 MB (60%)
4.2 MB
1.7 MB
In fact, the total size of Planit.fr main page is 4.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. CSS take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 528.4 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 248.9 kB, which is 42% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 528.4 kB or 90% of the original size.
Potential reduce by 33 B
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Planit images are well optimized though.
Potential reduce by 13.6 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 13.6 kB or 33% of the original size.
Potential reduce by 2.0 MB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Planit.fr needs all CSS files to be minified and compressed as it can save up to 2.0 MB or 98% of the original size.
Number of requests can be reduced by 22 (31%)
71
49
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Planit. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.verosoftware.fr
174 ms
production-software
1984 ms
VisitorIdentification.js
196 ms
jquery-ui.min.css
44 ms
coreRefresh.min.css
56 ms
coveoStyles.min.css
306 ms
owl.carousel.min.css
50 ms
owl.theme.default.min.css
62 ms
font-awesome.min.css
39 ms
animate.min.css
408 ms
jquery.min.js
62 ms
OtAutoBlock.js
48 ms
otSDKStub.js
62 ms
CoveoFullSearch.css
38 ms
CoveoForSitecore.css
485 ms
CoveoJsSearch.Lazy.min.js
41 ms
CoveoForSitecore.Lazy.min.js
484 ms
fr.js
546 ms
addthis_widget.js
78 ms
metrology.all.min.js
12 ms
jquery-ui.min.js
10 ms
owl.carousel.min.js
9 ms
jquery.rwdImageMaps.min.js
10 ms
wow.min.js
13 ms
ac21b822-14f0-44a7-b80d-367ca2e6def1.json
57 ms
arrow-dropdown.svg
52 ms
css
64 ms
Pod_AG.ashx
153 ms
Pod_PPM.ashx
518 ms
Pod_PI.ashx
518 ms
Pod_GEO.ashx
512 ms
Pod_MI.ashx
512 ms
Pod_MIN.ashx
202 ms
Pod_SI.ashx
516 ms
module-1.ashx
517 ms
HomePg_Pod-800x428_Our-Story.ashx
814 ms
HomePg_Pod-800x428_Solutions.ashx
898 ms
Hexagon_HomePage_Pod_3_Sustainability.ashx
714 ms
lang-map-eu.ashx
620 ms
lang-map-ame.ashx
619 ms
lang-map-asi.ashx
620 ms
hexagon.ashx
840 ms
Aerospace-teaser3.ashx
747 ms
Case-Studies-teaser.ashx
833 ms
Applications-teaser.ashx
828 ms
About-SFx-Hero.ashx
957 ms
module-1.ashx
932 ms
Service_and_support_teaser.ashx
945 ms
Open_Postions_Pod_800x428.ashx
955 ms
Events-teaser.ashx
1031 ms
Contact_us_teaser.ashx
1020 ms
Remote%20monitoring%20for%20CNC%20machines.ashx
1407 ms
Now-Hexagons-Production-Software--Marquee.ashx
1315 ms
Hexagon-MI-PS-POD-CAD-CAM-Software.ashx
1081 ms
Hexagon-MI-PS-POD-CNC-Simulation-Software.ashx
1093 ms
Hexagon-MI-PS-POD-Factory-Automation--Software.ashx
1156 ms
Letters_Pod_800x428.ashx
1148 ms
hxgn-akkurat-web-regular.woff
13 ms
new-inner-slider-theme.jpg
8 ms
arrows-carousel.png
43 ms
arrow-cta-blue.svg
267 ms
hexagon_facebook_icon_white.svg
290 ms
hexagon_facebook_icon_blue.svg
293 ms
Hexagon_Linkedin_icon_white.svg
293 ms
hexagon_linkedin_icon_blue.svg
300 ms
hexagon_twitter_icon_white.svg
302 ms
hexagon_twitter_icon_blue.svg
298 ms
hexagon_youtube_icon_white.svg
295 ms
hexagon_youtube_icon_blue.svg
294 ms
hexagon_ig_icon_white.svg
296 ms
hexagon_ig_icon_blue.svg
298 ms
hxgn-akkurat-web-black.woff
265 ms
hxgn-akkurat-web-bold.woff
281 ms
icon-close-white.svg
37 ms
arrow-cta-white.svg
37 ms
icons-sprite.png
39 ms
planit.fr accessibility score
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.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
[role]s do not have all required [aria-*] attributes
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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.
Impact
Issue
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
planit.fr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
planit.fr SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not 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 more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
FR
FR
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Planit.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Planit.fr main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
planit.fr
Open Graph data is detected on the main page of Planit. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: