2.1 sec in total
254 ms
1.5 sec
311 ms
Welcome to porte.fr homepage info - get ready to check PORTE best content right away, or after learning these important things about porte.fr
Conception, étude, réalisation: Tôlerie - Mécano soudure - Réseaux siphoïdes/gravitaires - Sécurisation de toiture
Visit porte.frWe analyzed Porte.fr page load time and found that the first response time was 254 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
porte.fr performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value11.1 s
0/100
25%
Value13.9 s
1/100
10%
Value4,340 ms
1/100
30%
Value0.107
88/100
15%
Value20.3 s
2/100
10%
254 ms
279 ms
83 ms
158 ms
159 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 96% of them (50 requests) were addressed to the original Porte.fr, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (563 ms) belongs to the original domain Porte.fr.
Page size can be reduced by 120.9 kB (39%)
310.8 kB
189.9 kB
In fact, the total size of Porte.fr main page is 310.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 146.9 kB which makes up the majority of the site volume.
Potential reduce by 14.0 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 2.2 kB, which is 12% 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 14.0 kB or 79% of the original size.
Potential reduce by 14.2 kB
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. PORTE images are well optimized though.
Potential reduce by 75.4 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 75.4 kB or 61% of the original size.
Potential reduce by 17.4 kB
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. Porte.fr needs all CSS files to be minified and compressed as it can save up to 17.4 kB or 77% of the original size.
Number of requests can be reduced by 17 (34%)
50
33
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PORTE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
porte.fr
254 ms
www.porte.fr
279 ms
reset.css
83 ms
960.css
158 ms
styles.css
159 ms
jquery.tools.min.js
243 ms
jquery.mailme.js
164 ms
jquery.lightbox-0.5.js
164 ms
jquery.lightbox-0.5.css
166 ms
porte.js
235 ms
bg_big.gif
103 ms
bg_global-big.jpg
179 ms
shadow.png
83 ms
RSS.png
82 ms
logo.png
84 ms
flags.gif
80 ms
menu_bg2.png
156 ms
slideshow_bg.png
159 ms
521_gm.JPG
167 ms
522_gm.JPG
169 ms
707_gm.JPG
186 ms
705_gm.JPG
236 ms
slideshow_counter.png
237 ms
btn_rea.png
255 ms
slider_btn.gif
251 ms
625_min2.jpg
260 ms
734_min2.jpg
271 ms
1000_min2.jpg
321 ms
985_min2.jpg
320 ms
574_min2.jpg
336 ms
624_min2.JPG
341 ms
628_min2.JPG
342 ms
633_min2.JPG
355 ms
931_min2.JPG
402 ms
631_min2.JPG
402 ms
580_min2.JPG
425 ms
568_min2.JPG
429 ms
635_min2.JPG
431 ms
844_min2.jpg
440 ms
763_min2.jpg
484 ms
653_min2.JPG
484 ms
925_min2.jpg
508 ms
puce.gif
509 ms
qualibat.gif
514 ms
770_min4.jpg
521 ms
ga.js
25 ms
bg_footer.gif
516 ms
__utm.gif
14 ms
footer_bg.jpg
563 ms
footer_limits.png
513 ms
greentic.gif
513 ms
print.css
84 ms
porte.fr accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
porte.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
General
Impact
Issue
Detected JavaScript libraries
porte.fr SEO score
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
FR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Porte.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Porte.fr main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
porte.fr
Open Graph description is not detected on the main page of PORTE. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: