4.5 sec in total
520 ms
3.8 sec
124 ms
Visit diapar.com now to see the best up-to-date DIAPAR content for France and also check out these interesting facts you probably never knew about diapar.com
Groupe Diapar : centrale d'achat alimentaire des supermarches G20, supermarches Diagonal, supermarches Sitis, superettes Votre Marché.
Visit diapar.comWe analyzed Diapar.com page load time and found that the first response time was 520 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
diapar.com performance score
name
value
score
weighting
Value1.7 s
91/100
10%
Value8.6 s
1/100
25%
Value5.9 s
48/100
10%
Value100 ms
98/100
30%
Value0.033
100/100
15%
Value6.8 s
55/100
10%
520 ms
24 ms
170 ms
165 ms
162 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 98% of them (101 requests) were addressed to the original Diapar.com, 1% (1 request) were made to Fonts.googleapis.com and 1% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Diapar.com.
Page size can be reduced by 300.9 kB (9%)
3.4 MB
3.1 MB
In fact, the total size of Diapar.com main page is 3.4 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. 70% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 11.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. This page needs HTML code to be minified as it can gain 4.0 kB, which is 29% 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 11.3 kB or 82% of the original size.
Potential reduce by 1.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. DIAPAR images are well optimized though.
Potential reduce by 155.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 155.6 kB or 73% of the original size.
Potential reduce by 132.8 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. Diapar.com needs all CSS files to be minified and compressed as it can save up to 132.8 kB or 84% of the original size.
Number of requests can be reduced by 20 (20%)
101
81
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DIAPAR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
diapar.com
520 ms
css
24 ms
bootstrap.css
170 ms
responsive.css
165 ms
theme-minimalist-round.css
162 ms
frontend.css
167 ms
jquery-1.8.0.min.js
261 ms
bootstrap.min.js
167 ms
twitter-bootstrap-hover-dropdown.min.js
242 ms
jquery.easing.1.2.js
242 ms
jquery.anythingslider.min.js
244 ms
jquery.anythingslider.fx.min.js
245 ms
preloadCssImages.js
273 ms
jquery.validate.min.js
324 ms
frontend.js
322 ms
logo-diapar.png
363 ms
picto-home.png
364 ms
btn-acces-client.png
367 ms
pin-travaux.png
368 ms
pin-communication.png
403 ms
pin-assortiment.png
404 ms
pin-amenagement.png
405 ms
logo-G20.png
406 ms
logo-diagonal.png
408 ms
logo-sitis.png
409 ms
logo-votre-marche.png
483 ms
bandeau.png
471 ms
bandeau.png
472 ms
bandeau.png
472 ms
bandeau.png
473 ms
bandeau.png
474 ms
bg.png
550 ms
image.png
754 ms
text.png
553 ms
logos.png
554 ms
bg.jpg
794 ms
image.png
555 ms
text.png
630 ms
bg.png
1032 ms
image.png
712 ms
text.png
634 ms
bg.jpg
1030 ms
text.png
715 ms
bg.jpg
887 ms
text.png
730 ms
rxxXUYj4oZ6Q5oDJFtEd6i3USBnSvpkopQaUR-2r7iU.ttf
5 ms
round-sprite.png
647 ms
enseignes.jpg
763 ms
groupe.jpg
199 ms
logistique.jpg
162 ms
marketing.jpg
161 ms
marketing-terrain.jpg
161 ms
top-bg.jpg
359 ms
top-bg.jpg
347 ms
bg.jpg
390 ms
bg.png
83 ms
bg.jpg
161 ms
bg.jpg
82 ms
bg.jpg
162 ms
bg.jpg
162 ms
orange.png
81 ms
rouge.png
82 ms
bleu.png
84 ms
rose.png
84 ms
trame.png
83 ms
trame.png
82 ms
trame.png
83 ms
trame.png
83 ms
trame.png
82 ms
example-bg.gif
82 ms
prospectus.png
84 ms
stop-rayon.png
83 ms
affiche.png
81 ms
line.png
82 ms
line-end.png
83 ms
cadre1.png
83 ms
cadre2.png
82 ms
cadre3.png
82 ms
cadre4.png
84 ms
cadre5.png
82 ms
cadre6.png
82 ms
cadre-2008.jpg
82 ms
g20.png
82 ms
diagonal.png
82 ms
sitis.png
83 ms
votre-marche.png
82 ms
pictos.png
82 ms
concept.png
82 ms
assortiment.png
82 ms
img-g20minutes.png
82 ms
communication.jpg
82 ms
pictos.png
83 ms
concept.png
83 ms
assortiment.png
83 ms
communication.jpg
84 ms
pictos.png
84 ms
concept.png
84 ms
assortiment.png
82 ms
communication.jpg
161 ms
bg.png
82 ms
btn-envoyer.png
82 ms
glyphicons-halflings.png
82 ms
glyphicons-halflings-white.png
83 ms
diapar.com accessibility score
diapar.com 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
diapar.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Diapar.com 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 Diapar.com 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.
diapar.com
Open Graph data is detected on the main page of DIAPAR. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: