4.3 sec in total
469 ms
3.1 sec
739 ms
Visit 5.ag now to see the best up-to-date 5 content and also check out these interesting facts you probably never knew about 5.ag
Tyre, tire, wheels, rins, accessories, wholesale, tyre dealers, tyre trade tyre100.de, tyre100.at, pneus100.fr
Visit 5.agWe analyzed 5.ag page load time and found that the first response time was 469 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
5.ag performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value5.2 s
23/100
25%
Value4.3 s
76/100
10%
Value440 ms
64/100
30%
Value0
100/100
15%
Value4.2 s
86/100
10%
469 ms
202 ms
460 ms
132 ms
272 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original 5.ag, 70% (42 requests) were made to Camodo.com and 27% (16 requests) were made to Static.camodo.com. The less responsive or slowest element that took the longest time to load (717 ms) relates to the external source Static.camodo.com.
Page size can be reduced by 62.3 kB (19%)
326.9 kB
264.6 kB
In fact, the total size of 5.ag main page is 326.9 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. 25% of websites need less resources to load. Images take 197.1 kB 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. This page needs HTML code to be minified as it can gain 5.7 kB, which is 20% 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 22.6 kB or 80% of the original size.
Potential reduce by 5.1 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. 5 images are well optimized though.
Potential reduce by 31.1 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 31.1 kB or 33% of the original size.
Potential reduce by 3.4 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. 5.ag needs all CSS files to be minified and compressed as it can save up to 3.4 kB or 51% of the original size.
Number of requests can be reduced by 28 (49%)
57
29
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 5. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
5.ag
469 ms
www.camodo.com
202 ms
www.camodo.com
460 ms
Camodo.css
132 ms
ticker-small.css
272 ms
jquery.min.js
717 ms
jquery-jrumble-1.3.min.js
539 ms
ticker.js
405 ms
MicrosoftAjax.js
668 ms
MicrosoftMvcAjax.js
494 ms
MicrosoftMvcValidation.js
499 ms
metanavi_shadow_corner_l_t.jpg
182 ms
metanavi_shadow_left.jpg
180 ms
metanavi_shadow_corner_l_b.jpg
180 ms
logo_150.jpg
185 ms
camodo_willkommen3.jpg
197 ms
vdat.png
184 ms
brv.jpg
195 ms
ihk2013.png
196 ms
de.png
195 ms
fr.png
197 ms
gb.png
196 ms
it.png
278 ms
es.png
279 ms
Tyre100_-_Reifen_-_Felgen_-_Autoteile_w240.png
285 ms
Pneus100_-_Pneus_-_Jantes_-_Accessoires_w240.png
286 ms
Pneumatici100_-_Pneumatici_-_Cerchioni_-_Ricambi_w240.png
289 ms
Neumaticos100_-_Neumaticos_-_Llantas_-_Accesorios_w240.png
290 ms
facebook_logo_likes.png
374 ms
metanavi_shadow_bottom.jpg
297 ms
metanavi_shadow_gap_t.jpg
304 ms
metanavi_shadow_gap.jpg
305 ms
metanavi_shadow_gap_b.jpg
306 ms
metanavi_shadow_corner_r_t.jpg
307 ms
metanavi_shadow_right.jpg
395 ms
metanavi_shadow_corner_r_b.jpg
395 ms
navi_effect.gif
399 ms
navi_shadow_top.jpg
406 ms
nav_bg.jpg
405 ms
divider.gif
404 ms
navi_shadow_bottom.jpg
490 ms
black40.png
491 ms
camodo_arrow.png
487 ms
json
422 ms
bg_footer_dark.png
472 ms
dark-list-separator.gif
345 ms
lady1.png
109 ms
reifen2.png
97 ms
warenkorb.png
101 ms
reifenlabel.png
173 ms
teamwork.png
242 ms
reifen_mit_eulabel_klein.png
269 ms
alurad.png
347 ms
kraftstoff.png
363 ms
schach.png
408 ms
alurad2.png
434 ms
einlagerung3.png
435 ms
reifen.png
435 ms
facebook.png
434 ms
terminreservierung.png
453 ms
5.ag accessibility score
5.ag 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
5.ag SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 5.ag can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that 5.ag 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.
5.ag
Open Graph description is not detected on the main page of 5. 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: