3 sec in total
269 ms
2.6 sec
171 ms
Click here to check amazing 2 Pour 1 content. Otherwise, check out these important facts you probably never knew about 2pour1.fr
Venez vite profiter de notre offre exceptionnelle! Pour un euros de plus, le second article vous est offert sur l'ensemble de notre catalogue fr linge de maison!
Visit 2pour1.frWe analyzed 2pour1.fr page load time and found that the first response time was 269 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
2pour1.fr performance score
name
value
score
weighting
Value1.8 s
89/100
10%
Value3.1 s
74/100
25%
Value2.0 s
99/100
10%
Value0 ms
100/100
30%
Value0.206
60/100
15%
Value1.8 s
100/100
10%
269 ms
586 ms
122 ms
171 ms
168 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 97% of them (71 requests) were addressed to the original 2pour1.fr, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (867 ms) belongs to the original domain 2pour1.fr.
Page size can be reduced by 763.0 kB (52%)
1.5 MB
699.8 kB
In fact, the total size of 2pour1.fr main page is 1.5 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. 50% of websites need less resources to load. Javascripts take 731.3 kB which makes up the majority of the site volume.
Potential reduce by 19.3 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 19.3 kB or 75% of the original size.
Potential reduce by 89.4 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. Obviously, 2 Pour 1 needs image optimization as it can save up to 89.4 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 571.9 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 571.9 kB or 78% of the original size.
Potential reduce by 82.3 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. 2pour1.fr needs all CSS files to be minified and compressed as it can save up to 82.3 kB or 84% of the original size.
Number of requests can be reduced by 44 (62%)
71
27
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 2 Pour 1. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
2pour1.fr
269 ms
www.2pour1.fr
586 ms
annuaire.css
122 ms
reset.css
171 ms
layout.css
168 ms
style.css
268 ms
type.css
163 ms
dd.css
166 ms
slider.css
206 ms
ddsmoothmenu.css
242 ms
ddsmoothmenu-v.css
248 ms
style.css
255 ms
lytebox.css
254 ms
sifr.css
291 ms
swfobject.js
356 ms
jquery.js
493 ms
ddsmoothmenu.js
344 ms
utils.js
340 ms
lytebox.js
363 ms
mailto.js
378 ms
jquery.dd.js
424 ms
jquery-1.4.js
608 ms
jquery-ui.js
602 ms
ui.tabs.css
449 ms
ui.tabs.js
467 ms
jquery.alerts.css
508 ms
jquery.alerts.js
546 ms
lytebox.css
551 ms
lytebox.js
631 ms
skin-carousel.css
593 ms
jquery.jcarousel.css
632 ms
jquery.jcarousel.js
640 ms
jquery.jqzoom1.0.1.js
677 ms
jqzoom.css
683 ms
forms.js
695 ms
search.js
697 ms
sifr.js
708 ms
fancy.css
697 ms
sifr-debug.js
651 ms
jqFancyTransitions.1.8.min.js
637 ms
header.jpg
263 ms
site_logo.jpg
273 ms
rechercher.jpg
116 ms
zoom_icon2.jpg
112 ms
icon1_thumb2.jpg
105 ms
icon2_thumb2.jpg
104 ms
icon9_thumb2.jpg
203 ms
mon_compte.jpg
198 ms
newsletter.jpg
208 ms
contact.jpg
219 ms
sitemap_icon.jpg
295 ms
mail_icon.jpg
296 ms
home_icon.jpg
307 ms
menu11.jpg
318 ms
panierBag.jpg
356 ms
spacer.jpg
377 ms
menuVertical1.jpg
412 ms
menuVertical2.jpg
393 ms
menuVertical3.jpg
481 ms
menuVertical4.jpg
435 ms
menuVertical5.jpg
461 ms
bandeau-2pr1-mai-002_thumb1.jpg
708 ms
bandeau-2pr1-mai-003_thumb1.jpg
643 ms
bandeau-2pr1-mai-004_thumb1.jpg
598 ms
bandeau-2pr1-mai-005_thumb1.jpg
616 ms
bandeau-2pr1-mai-009_thumb1.jpg
635 ms
bandeau-2pr1-mai-0010_thumb1.jpg
651 ms
peace_love_rose_poudre_(copier)_thumb1.jpg
771 ms
zoom_taie_diamond__(copier)_thumb1.jpg
867 ms
ga.js
23 ms
line.jpg
650 ms
__utm.gif
23 ms
print.css
94 ms
2pour1.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.
2pour1.fr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
2pour1.fr SEO score
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
FR
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 2pour1.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 2pour1.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.
2pour1.fr
Open Graph description is not detected on the main page of 2 Pour 1. 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: