4.8 sec in total
420 ms
4.2 sec
174 ms
Click here to check amazing X Prime content. Otherwise, check out these important facts you probably never knew about x-prime.com
À l’épreuve de l’époque et du nouveau consommateur Jamais les marques n’ont eu affaire à autant de défiance ou d’indifférence. À l’heure où elles font face à une disruption tout azi...
Visit x-prime.comWe analyzed X-prime.com page load time and found that the first response time was 420 ms and then it took 4.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.
x-prime.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value4.6 s
35/100
25%
Value4.8 s
67/100
10%
Value0 ms
100/100
30%
Value0.144
78/100
15%
Value4.5 s
83/100
10%
420 ms
521 ms
161 ms
163 ms
164 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original X-prime.com, 61% (59 requests) were made to Xprimegroupe.com and 21% (20 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Xprimegroupe.com.
Page size can be reduced by 674.1 kB (15%)
4.6 MB
3.9 MB
In fact, the total size of X-prime.com main page is 4.6 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. Images take 4.3 MB which makes up the majority of the site volume.
Potential reduce by 22.6 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 22.6 kB or 75% of the original size.
Potential reduce by 477.0 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, X Prime needs image optimization as it can save up to 477.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 98.8 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 98.8 kB or 62% of the original size.
Potential reduce by 75.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. X-prime.com needs all CSS files to be minified and compressed as it can save up to 75.8 kB or 84% of the original size.
Number of requests can be reduced by 35 (39%)
90
55
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of X Prime. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
x-prime.com
420 ms
www.xprimegroupe.com
521 ms
system.messages.css
161 ms
field.css
163 ms
views.css
164 ms
ctools.css
168 ms
reset.css
166 ms
base.css
165 ms
styles.css
335 ms
jquery.jscrollpane.css
250 ms
drupal.css
248 ms
jquery.js
496 ms
jquery.once.js
246 ms
drupal.js
329 ms
fr_GYYvCoB1FZSmyRozL9tzbPVyDrJL_TayMIRvVzxz9No.js
330 ms
hp.js
331 ms
css_browser_selector.js
331 ms
masonry.pkgd.min.js
506 ms
common.js
414 ms
jquery.scrollTo-min.js
414 ms
ga.js
56 ms
logo_xpg_2.png
112 ms
bmw-i3_hp_0.jpg
828 ms
bmw_logo_white_hp.png
113 ms
hp_airbus_a350.jpg
980 ms
logo_airubs_a350_xw.png
164 ms
flv_hp-contrib.jpg
975 ms
logo_flv_0.png
171 ms
hp_visu-st-gobain.jpg
1076 ms
logo_saint_gobain.png
248 ms
hp_visu-krug.jpg
828 ms
logo_krug.png
333 ms
awwwards_siteoftheday_w_left.png
416 ms
footer_facebook_2.png
498 ms
footer_instagram_2.png
582 ms
footer_tumblr_2.png
665 ms
footer_linkedIn_2.png
748 ms
footer_youtube_2.png
829 ms
footer_slideshare_2.png
908 ms
footer_nl_2.png
910 ms
footer_rond_hot_news.png
913 ms
public
997 ms
footer_rond_facebook.png
992 ms
all.js
50 ms
xp_social_callback
1024 ms
puce_nav_s.png
1009 ms
puce_nav_jaune_s.png
1013 ms
fl_d_rond_blanc.png
1029 ms
bulle.png
1031 ms
motif_grille.png
1090 ms
frise.png
1093 ms
frise_on.png
1103 ms
frise_off.png
1108 ms
lien_hot_news.gif
1109 ms
dernier_tweet_gauche.gif
1111 ms
dernier_tweet_droite.gif
1171 ms
temoin_off.png
1173 ms
temoin_on.png
1184 ms
__utm.gif
22 ms
__utm.gif
13 ms
125 ms
xd_arbiter.php
39 ms
xd_arbiter.php
47 ms
public
84 ms
public
84 ms
public
84 ms
public
84 ms
xd_arbiter.php
6 ms
fan.php
497 ms
ebiMDO3r-8l.css
23 ms
wakJkBioHgT.css
25 ms
k5BhlqovqZn.css
31 ms
q68gy-v_YMF.js
30 ms
8w-1WQE8wsO.js
29 ms
0wM5s1Khldu.js
28 ms
1bNoFZUdlYZ.js
56 ms
OloiM1PZafe.js
28 ms
LTv6ZK-5zxz.js
63 ms
1FCa-btixu2.js
59 ms
Oagsvfb4VWi.js
60 ms
pObvZSrFc_4.js
59 ms
Nn19HjwCsOL.js
60 ms
H3EKDTObx05.js
60 ms
OZFAYTv-ZUg.js
60 ms
12734126_1267694989913214_6116006787490789583_n.jpg
91 ms
1513313_796849733664411_2552350_n.jpg
15 ms
10984229_136699223355183_5607261389056524710_n.jpg
17 ms
562423_10150856569841356_648406971_n.jpg
14 ms
11825947_987946114559947_967634057571977644_n.jpg
16 ms
12717329_1582464745411441_6253596794921329639_n.jpg
14 ms
1379841_10150004552801901_469209496895221757_n.jpg
12 ms
12274687_10207801130806995_6134640123495105160_n.jpg
15 ms
wL6VQj7Ab77.png
8 ms
s7jcwEQH7Sx.png
10 ms
gxbPuQdXIZP.png
6 ms
I6-MnjEovm5.js
3 ms
pQrUxxo5oQp.js
4 ms
x-prime.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
x-prime.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
x-prime.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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 X-prime.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 X-prime.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.
x-prime.com
Open Graph data is detected on the main page of X Prime. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: