6.7 sec in total
1.1 sec
4.9 sec
628 ms
Click here to check amazing Ordi content. Otherwise, check out these important facts you probably never knew about ordi.com
Boutique propulsée par PrestaShop
Visit ordi.comWe analyzed Ordi.com page load time and found that the first response time was 1.1 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
ordi.com performance score
name
value
score
weighting
Value3.7 s
28/100
10%
Value4.5 s
37/100
25%
Value5.6 s
54/100
10%
Value260 ms
84/100
30%
Value0.249
50/100
15%
Value8.0 s
43/100
10%
1118 ms
524 ms
69 ms
116 ms
371 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 40% of them (27 requests) were addressed to the original Ordi.com, 29% (20 requests) were made to Static.xx.fbcdn.net and 13% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Ordi.com.
Page size can be reduced by 353.4 kB (42%)
850.5 kB
497.1 kB
In fact, the total size of Ordi.com main page is 850.5 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. 55% of websites need less resources to load. Images take 420.5 kB which makes up the majority of the site volume.
Potential reduce by 118.7 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 118.7 kB or 88% of the original size.
Potential reduce by 566 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. Ordi images are well optimized though.
Potential reduce by 33.5 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 33.5 kB or 60% of the original size.
Potential reduce by 200.7 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. Ordi.com needs all CSS files to be minified and compressed as it can save up to 200.7 kB or 84% of the original size.
Number of requests can be reduced by 22 (34%)
65
43
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ordi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
index.php
1118 ms
v_21_53b268b735c4b3bfedd9b7de67334a72_all.css
524 ms
css
69 ms
css
116 ms
ordicom-sa-logo-1435845665.jpg
371 ms
7941476e1a12a31752a0681bc2a220e8b844f197_galaxys7-slider.jpg
264 ms
94995f0ad08fa09334b2c748603082381d56de89_ipad-slider2.jpg
806 ms
be74e360dcf92cf59e52c0cf039dc89b0397a3b8_surface4.jpg
806 ms
0a7be24a6670ad1dee3c0aba96ad0b16486dd607_Newplay5.jpg
802 ms
8b07503e6cee7f2b328aa2ea5732833e6e7d1661_ecotank-slider.jpg
810 ms
fc342e00ecc073df0b985a45e35360fb8320681f_sonos-slider.jpg
810 ms
b8dea4cecba4e2409bde7196b6c43c47698f91aa_imac-5k.jpg
808 ms
7b576a36f61dc2c3a22af54e3955b48ca20d8039_surface4.jpg
814 ms
1028-home_default.jpg
812 ms
1027-home_default.jpg
758 ms
1025-home_default.jpg
749 ms
1024-home_default.jpg
788 ms
1023-home_default.jpg
751 ms
1022-home_default.jpg
778 ms
1019-home_default.jpg
751 ms
1018-home_default.jpg
778 ms
422-home_default.jpg
776 ms
427-home_default.jpg
822 ms
268-home_default.jpg
821 ms
998-home_default.jpg
820 ms
v_22_7133809d5c346d638bd9cbaec2c7ce09.js
1039 ms
price-container-bg.png
200 ms
fontawesome-webfont.woff
265 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
55 ms
analytics.js
549 ms
all.js
198 ms
bx_loader.gif
183 ms
ec.js
47 ms
195 ms
collect
26 ms
xd_arbiter.php
60 ms
xd_arbiter.php
111 ms
ping
86 ms
like_box.php
197 ms
xwWG67BZFLW.css
71 ms
92jR-n5wPxz.css
84 ms
dBTs0i6aRqX.css
176 ms
SRSW8M763HA.js
315 ms
ullQFyhrQFI.js
287 ms
y97Ig99UVTs.js
213 ms
KHAtULXOQuz.js
193 ms
XlY_wsDnClE.js
273 ms
rR4Qw0p7TFQ.js
469 ms
ULtnh-HfQSw.js
370 ms
d_-F4IIjJo3.js
288 ms
FOagnU9QnXq.js
380 ms
Cw6QosZRsiU.js
373 ms
i8XO-4kv8i7.js
372 ms
z5eMxBRE-Ji.js
374 ms
7YklgZdHLYS.js
376 ms
936034_563728050386819_945536620_n.jpg
261 ms
1522197_563728120386812_1356231354_n.jpg
241 ms
10410557_1063790373682212_3211754327560376404_n.jpg
237 ms
12240143_194086740972414_4925484072795644959_n.jpg
238 ms
1484722_746335365395530_191863196_n.jpg
232 ms
943992_973907922687514_2057822307830739491_n.jpg
222 ms
12512404_10153573198831446_1034946866549819008_n.jpg
233 ms
12961581_1594649754185137_5896780820805445257_n.jpg
301 ms
12802925_10208055263326791_5257010322038407398_n.jpg
248 ms
wL6VQj7Ab77.png
173 ms
1JLnMyDN79z.png
171 ms
FASTu8Ostla.png
33 ms
VXcANLwwL5J.js
25 ms
ordi.com accessibility score
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
Form elements do not have associated labels
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
ordi.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
ordi.com 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
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ordi.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 Ordi.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.
ordi.com
Open Graph description is not detected on the main page of Ordi. 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: