4.9 sec in total
1.1 sec
3.1 sec
646 ms
Click here to check amazing PACE content for Germany. Otherwise, check out these important facts you probably never knew about pace.car
PACE entwickelt die Connected Fueling Plattform und die Tank-App PACE Drive für bargeldloses Bezahlen an der Tankstelle mit dem Handy. Jetzt kostenlos testen!
Visit pace.carWe analyzed Pace.car page load time and found that the first response time was 1.1 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
pace.car performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value4.6 s
34/100
25%
Value4.8 s
67/100
10%
Value20 ms
100/100
30%
Value0.259
47/100
15%
Value4.9 s
77/100
10%
1131 ms
544 ms
122 ms
97 ms
192 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 82% of them (31 requests) were addressed to the original Pace.car, 5% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Pace.car.
Page size can be reduced by 177.1 kB (16%)
1.1 MB
954.6 kB
In fact, the total size of Pace.car main page is 1.1 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. 30% of websites need less resources to load. Images take 856.6 kB which makes up the majority of the site volume.
Potential reduce by 8.8 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 8.8 kB or 60% of the original size.
Potential reduce by 1.6 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. PACE images are well optimized though.
Potential reduce by 120.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 120.9 kB or 60% of the original size.
Potential reduce by 45.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. Pace.car needs all CSS files to be minified and compressed as it can save up to 45.8 kB or 77% of the original size.
Number of requests can be reduced by 4 (13%)
30
26
The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PACE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
pace.car
1131 ms
www.pace.car
544 ms
de
122 ms
fold-ff8e324db21ae99b5ecc6d0a5650f8614258a29221c136e05f7fcf60317aff9c.css
97 ms
application-c593de2c1ee7b9ddeef574292540483edc19df4540bcbe2a72c4045bb0537849.css
192 ms
application-58783b215f66abc625f4620e3f213c4d515d00272680864bbe8d7c6a43118961.js
380 ms
dongle-44c22fb78a4630dc74e82f4f51f946398ea8631ccd942a11c930554e2df208c8.png
290 ms
badge_89_euro-5c9cc4fbbd6214671fd0e36b432481ba11f9378f8553ad9db8dfd05f595d2845.png
106 ms
box_phone_ph-a4af3afad22f9257d6e8c7d7570e2cc4784de05d14642992a9e8f10ab57df2e0.png
106 ms
box_ph-e22c871aa47eb9ec5cc856794ec44f1e74c594249de6dc3ab76911e8549867c4.png
190 ms
emergency-39267f7e23ea319116d89b11e37928f7001fe7b263e6198ef8af361dc310c90f.svg
206 ms
money-c08c3b34f88b97fc8cd0902132aadceb697418f0df998140b564bff2904c9753.svg
284 ms
diagnosis-f7a73bb81f832a1161c5740eb4978740f771392272c4de5bcfd94be71aa74837.svg
286 ms
find_my_car-3e43d68f87fe8cfaedfa78e53352cfddbedb8063ccef9ea5190ebc16c76041d6.svg
291 ms
book-4c6118f52c7083783e10f76165d2d8ec7fe528887e55d48fc179b6f24b49d698.svg
306 ms
traffic_lights-8183e93e69d53b786d27e4eeada59cff9ecb4a80dc8fd259d5caeb3ee2d4a3ea.svg
313 ms
gas_station-78354a62b6d74b3dbdc096caeebefda67043c07b56eb2982b4035960ff9896d6.svg
377 ms
dashboard-eb957df207914f741aa0e31ea6468213b66ecd6b26e757fa033499d370c7fb25.svg
380 ms
drop-2ab4dafd09a0441539d3db4b11cea5c00e0412da391d7ddb1621330db3785f98.svg
383 ms
drive_mode_optimized-461c5da49823690293a20f25a8ae873d1ca2838aac4228c3d99b49d9d80f1bc2.png
572 ms
timeline_mode_optimized-9e186381e614adaad37433a7b63da2a9723ab366babb6b4e7cf1ffc5ef043b0b.png
708 ms
dashboard-cc9ec343b89a454d90482c605fa6e96b6c740ddf78537e8f5c8df35a1399fc0f.jpg
516 ms
logo_black-36eed40e02bb765d686da562ccb81f14234a61866f66addcd2a2c59b40634c76.svg
470 ms
gtm.js
89 ms
piwik.js
622 ms
cover_optimized-d591a8c9690ca2eccf42e0916fb62e4fcedff11e907f5733f6901b3cfd5cc96f.jpg
803 ms
box-628808fddf3f2f1e21c3d2e73e0f83481dfce03097fc0ac9767110565e57daef.png
621 ms
street_2-c16150ab807a86b1652c9ccef99036de606f32ef5831506958c4e2621baa43b5.jpg
893 ms
2FFD34_3_0-e8fab8b8b7527f5ded00a7049c28100ae3a7c475cfb507f78e66bcedb36efcf8.woff
673 ms
2FFD34_2_0-d4455b750f9ddc0a2f4505107a63b3d8ca8f7500e2da73da6d39e0879ac2ca8e.woff
621 ms
2FFD34_1_0-88d22e18dc863a3b9e42b0d914678a9a9be7348b9c3e738adc7202c88dde6c7e.woff
712 ms
2FFD34_4_0-799d685d154e1c1ee289df15e759cca02d4b0dad0af2c517ef711d309b510e91.woff
719 ms
2FFD34_0_0-3dcda83b452018fb7ac51105c86dbcd42ef5980230be5036f1321fabce83a0d6.woff
760 ms
analytics.js
22 ms
fbevents.js
187 ms
collect
3 ms
collect
53 ms
24 ms
pace.car 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
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
pace.car best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
pace.car SEO score
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
DE
DE
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pace.car can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Pace.car main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
pace.car
Open Graph description is not detected on the main page of PACE. 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: