4.1 sec in total
39 ms
3.5 sec
634 ms
Visit infiniti.de now to see the best up-to-date INFINITI content for Germany and also check out these interesting facts you probably never knew about infiniti.de
Sie suchen Service und Unterstützung für Ihren INFINITI SUV, Crossover oder Ihre Limousine? Finden Sie das nächstgelegene INFINITI-Center für Fahrzeugservice, Support und Fahrzeuginformationen.
Visit infiniti.deWe analyzed Infiniti.de page load time and found that the first response time was 39 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
infiniti.de performance score
name
value
score
weighting
Value6.9 s
1/100
10%
Value18.2 s
0/100
25%
Value8.2 s
20/100
10%
Value11,700 ms
0/100
30%
Value1.147
1/100
15%
Value28.9 s
0/100
10%
39 ms
144 ms
220 ms
191 ms
177 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Infiniti.de, 19% (16 requests) were made to Libs.infiniti-cdn.net and 13% (11 requests) were made to Infiniti-cdn.net. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Infiniti-cdn.net.
Page size can be reduced by 3.0 MB (46%)
6.5 MB
3.5 MB
In fact, the total size of Infiniti.de main page is 6.5 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. 60% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 95.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. This page needs HTML code to be minified as it can gain 36.1 kB, which is 33% 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 95.5 kB or 87% of the original size.
Potential reduce by 774.3 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, INFINITI needs image optimization as it can save up to 774.3 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.4 MB
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 1.4 MB or 70% of the original size.
Potential reduce by 750.9 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. Infiniti.de needs all CSS files to be minified and compressed as it can save up to 750.9 kB or 83% of the original size.
Number of requests can be reduced by 50 (66%)
76
26
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of INFINITI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.infiniti.de
39 ms
fonts-latin-basic.min.css
144 ms
small.min.css
220 ms
medium.min.css
191 ms
large.min.css
177 ms
adrum.min.js
194 ms
modernizr.min.js
176 ms
intl.js
193 ms
de-DE.js
339 ms
satelliteLib-ed0026b3a8941c1c95cbb853ee3be30caa8d5967.js
68 ms
main.min.js
363 ms
Infiniti_logo.png
297 ms
droidsans-webfont.woff
29 ms
infinitimetapro-normal-webfont.woff
113 ms
infinitimetapro-medium-webfont.woff
113 ms
Infiniti-Global.woff
113 ms
infinitimetapro-book-webfont.woff
101 ms
gtm.js
282 ms
infinitimetapro-bold-webfont.woff
170 ms
satellite-568e43a064746d25a900c4c8.js
151 ms
satellite-5698ecb564746d757f000205.js
150 ms
satellite-55fc29ee33396342860007c3.js
186 ms
s-code-contents-cdde1fa750731569ff85267dad78f817f348b327.js
186 ms
satellite-55b234df32363600170000f4.js
184 ms
widgets.js
125 ms
socialmediadisplay_e.social.feeds.json
397 ms
v24Embedded.js
549 ms
abde_infiniti.php
568 ms
38858_IN_HomepageBanner_3000x1292.jpg.ximg.full.hero.jpg
270 ms
39477_Challenger_series_page_banner_3000x1292_clean.jpg.ximg.full.hero.jpg
320 ms
39352_IN_3000x1292_v2.jpg.ximg.full.hero.jpg
405 ms
39001_INF_WEB_3000x1292_UrbanStyle_v6.jpg.ximg.full.hero.jpg
313 ms
38320_QX70_Ultimate_3000x1292_v2.png.ximg.full.hero.png
621 ms
39310_INF_3000x1292.png.ximg.full.hero.png
794 ms
GM-Infinti-F1-3000x1292.jpg.ximg.full.hero.jpg
428 ms
39352_Infiniti_3000x1292px_V2.jpg.ximg.full.hero.jpg
428 ms
36156_IN_Helios_3072x1728_V3_011.jpg.ximg.l_6_m.smart.jpg
492 ms
q30-main-header-v3-3072x1728.png.ximg.l_6_m.smart.png
1643 ms
print.min.css
68 ms
satellite-5698ef4b64746d6f5a0002cc.js
62 ms
satellite-55b234df32363600170000f5.js
22 ms
id
193 ms
analytics.js
175 ms
ebOneTag.js
127 ms
v24Embedded.js
441 ms
fbevents.js
116 ms
4909.js
160 ms
id
172 ms
132 ms
Serving
187 ms
collect
85 ms
collect
149 ms
platform.js
171 ms
hqdefault.jpg
132 ms
photo.jpg
114 ms
hqdefault.jpg
151 ms
hqdefault.jpg
169 ms
s55550498412922
38 ms
up_loader.1.1.0.js
107 ms
conversion.js
80 ms
529ame2076.js
95 ms
activityi;src=4333645;type=sales;cat=emkenpq3;qty=[Quantity];cost=[Revenue];ord=[OrderID]
93 ms
layer_question.php
128 ms
49 ms
tp
15 ms
up
45 ms
37 ms
25 ms
universal_pixel.1.1.1.js
5 ms
pixel
48 ms
iui3
190 ms
match
5 ms
generic
5 ms
5 ms
dest5.html
28 ms
PageBehaviour.gif
256 ms
PageBehaviour.gif
660 ms
adrum-ext.ca98cd9e9bc9be02e16c4d7fb16dbb51.js
90 ms
LoggerPage.gif
166 ms
OpeningHours.gif
136 ms
CookiesEnabled.gif
236 ms
default-5.3.1.css
29 ms
default.css
136 ms
Resources.gif
267 ms
css
57 ms
handshake.js
237 ms
infiniti.de 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
infiniti.de 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
Missing source maps for large first-party JavaScript
infiniti.de 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 Infiniti.de 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 Infiniti.de 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.
infiniti.de
Open Graph data is detected on the main page of INFINITI. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: