9.6 sec in total
375 ms
8.7 sec
559 ms
Welcome to pieces2mobile.com homepage info - get ready to check Pieces2mobile best content for France right away, or after learning these important things about pieces2mobile.com
Pieces2mobile, la Référence des sites de vente de Pièces détachées et d'accessoires pour Smartphones et tablettes. Prix de gros pour les professionnels. Envois rapides. Larges stocks. SAV de qualité. ...
Visit pieces2mobile.comWe analyzed Pieces2mobile.com page load time and found that the first response time was 375 ms and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
pieces2mobile.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value9.0 s
1/100
25%
Value16.5 s
0/100
10%
Value5,170 ms
0/100
30%
Value0.747
6/100
15%
Value15.8 s
6/100
10%
375 ms
2447 ms
201 ms
270 ms
196 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 89% of them (91 requests) were addressed to the original Pieces2mobile.com, 5% (5 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Pieces2mobile.com.
Page size can be reduced by 1.6 MB (44%)
3.7 MB
2.1 MB
In fact, the total size of Pieces2mobile.com main page is 3.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 611.5 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 611.5 kB or 92% of the original size.
Potential reduce by 104.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. Pieces2mobile images are well optimized though.
Potential reduce by 467.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 467.9 kB or 74% of the original size.
Potential reduce by 447.0 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. Pieces2mobile.com needs all CSS files to be minified and compressed as it can save up to 447.0 kB or 86% of the original size.
Number of requests can be reduced by 38 (41%)
92
54
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pieces2mobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
pieces2mobile.com
375 ms
www.pieces2mobile.com
2447 ms
widgets.css
201 ms
styles.css
270 ms
general.css
196 ms
productslist.css
204 ms
productsscroller.css
200 ms
custom.css
252 ms
chronorelais.css
292 ms
onebyone.css
285 ms
animate.css
290 ms
responsive.css
286 ms
prototype.js
429 ms
ccard.js
351 ms
validation.js
366 ms
builder.js
367 ms
effects.js
371 ms
dragdrop.js
371 ms
controls.js
455 ms
slider.js
457 ms
js.js
457 ms
form.js
461 ms
translate.js
459 ms
cookies.js
512 ms
campaignCatcher.js
523 ms
jquery-1.8.2.min.js
629 ms
bootstrap.min.js
542 ms
bootstrap-tooltip.js
544 ms
jquery.mtlib.js
658 ms
jquery.selectbox-0.2.js
595 ms
jquery.1.8.2.min.js
699 ms
noConflict.js
656 ms
jquery.onebyone.js
645 ms
jquery.touchwipe.js
662 ms
bootstrap.min.css
698 ms
custom-bootstrap.css
707 ms
bootstrap-responsive.min.css
708 ms
css
24 ms
getgeotrustsslseal
73 ms
styles-responsive.css
577 ms
ga.js
84 ms
bg_1.png
185 ms
logo.png
132 ms
blank.gif
129 ms
promo_1.jpg
672 ms
promo_2.jpg
681 ms
sony_xperia_z3_compact_d5803_pantalla_completa.jpg
666 ms
sony_xperia_z3_compact_d5803_pantalla_completa.jpg
670 ms
loading.gif
206 ms
ecran-tactilelcd-xperia-z3-l55t-noir.jpg
258 ms
ecran-tactilelcd-xperia-z3-l55t-noir.jpg
666 ms
z2_lcd_1.jpg
668 ms
z2_lcd_1.jpg
670 ms
ecran_z1_compact.jpg
675 ms
ecran_z1_compact.jpg
671 ms
zenfone_2.jpg
676 ms
zenfone_2.jpg
671 ms
img_2884.jpg
677 ms
img_2884.jpg
674 ms
oneplus_one_95e.jpg
674 ms
oneplus_one_95e.jpg
680 ms
acer_z150_59e.jpg
676 ms
acer_z150_59e.jpg
687 ms
apple.png
677 ms
samsung.png
677 ms
nokia.png
678 ms
blackberry.png
686 ms
htc.png
697 ms
lg.png
701 ms
sony_ericsson.png
705 ms
acer.png
712 ms
asus.png
775 ms
payement_icons.png
860 ms
support.png
714 ms
email.png
719 ms
IgZJs4-7SA1XX_edsoXWog.ttf
51 ms
DXI1ORHCpsQm3Vp6mXoaTS3USBnSvpkopQaUR-2r7iU.ttf
100 ms
MTP_ySUJH_bn48VBG8sNSi3USBnSvpkopQaUR-2r7iU.ttf
123 ms
k3k702ZOKiLJc3WVjuplzC3USBnSvpkopQaUR-2r7iU.ttf
124 ms
EInbV5DfGHOiMmvb1Xr-hi3USBnSvpkopQaUR-2r7iU.ttf
124 ms
__utm.gif
17 ms
search-icon.png
677 ms
mt-compare.png
673 ms
cart-icon.png
733 ms
collect
104 ms
loading.gif
700 ms
bg-tranfer-name.png
685 ms
mt-list.png
685 ms
ga-audiences
424 ms
mt-arrow-scroll.png
635 ms
loading.gif
291 ms
loading.gif
565 ms
btn-newsletter.png
299 ms
social.png
306 ms
list-style.jpg
308 ms
316 ms
up-arrow.png
370 ms
bg-li-menu-parent.png
379 ms
print.css
90 ms
partse.jpg
3939 ms
slider_partse_com_1.jpg
624 ms
nav.png
88 ms
pieces2mobile.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role]s do not have all required [aria-*] attributes
[aria-*] attributes are not valid or misspelled
ARIA IDs are not unique
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
[id] attributes on active, focusable elements are not unique
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.
pieces2mobile.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
Missing source maps for large first-party JavaScript
pieces2mobile.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
Tap targets are not sized appropriately
FR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pieces2mobile.com 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 Pieces2mobile.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.
pieces2mobile.com
Open Graph data is detected on the main page of Pieces2mobile. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: