2.5 sec in total
316 ms
1.9 sec
293 ms
Visit 4gps.de now to see the best up-to-date 4GPS content for Germany and also check out these interesting facts you probably never knew about 4gps.de
Visit 4gps.deWe analyzed 4gps.de page load time and found that the first response time was 316 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
4gps.de performance score
name
value
score
weighting
Value1.5 s
96/100
10%
Value1.5 s
100/100
25%
Value1.5 s
100/100
10%
Value0 ms
100/100
30%
Value0.002
100/100
15%
Value2.4 s
99/100
10%
316 ms
98 ms
30 ms
439 ms
194 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 28% of them (18 requests) were addressed to the original 4gps.de, 38% (24 requests) were made to Maps.google.com and 13% (8 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (439 ms) relates to the external source Schmuckschmiede.com.
Page size can be reduced by 371.8 kB (42%)
881.1 kB
509.3 kB
In fact, the total size of 4gps.de main page is 881.1 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. 60% of websites need less resources to load. Javascripts take 483.5 kB which makes up the majority of the site volume.
Potential reduce by 40.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 40.8 kB or 80% of the original size.
Potential reduce by 6.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. 4GPS images are well optimized though.
Potential reduce by 323.5 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 323.5 kB or 67% of the original size.
Potential reduce by 1.1 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. 4gps.de needs all CSS files to be minified and compressed as it can save up to 1.1 kB or 68% of the original size.
Number of requests can be reduced by 29 (52%)
56
27
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 4GPS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
4gps.de
316 ms
my.css
98 ms
maps
30 ms
getloc.php
439 ms
4gps.js
194 ms
redcoon-home.jpg
401 ms
count.php
347 ms
logo.jpg
100 ms
trans.gif
158 ms
4gpsoverview.jpg
193 ms
o2.gif
194 ms
new.gif
196 ms
arr.gif
200 ms
map_find.gif
199 ms
map_ins.gif
251 ms
map_del.gif
287 ms
save.gif
288 ms
llt.gif
292 ms
lt.gif
296 ms
gt.gif
296 ms
gtl.gif
346 ms
map_add.gif
383 ms
common1-redcoon-de-234x060.gif
206 ms
notFound
230 ms
mehr-tanken.de
244 ms
common.js
17 ms
map.js
19 ms
overlay.js
16 ms
util.js
15 ms
geocoder.js
11 ms
StaticMapService.GetMapImage
298 ms
onion.js
43 ms
ViewportInfoService.GetViewportInfo
130 ms
stats.js
25 ms
controls.js
17 ms
infowindow.js
16 ms
transparent.png
53 ms
css
47 ms
marker.js
25 ms
google4.png
28 ms
mapcnt6.png
26 ms
sv5.png
27 ms
tmapctrl.png
33 ms
cb_scout5.png
33 ms
tmapctrl4.png
30 ms
imgs8.png
31 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
25 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
27 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
29 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
28 ms
vt
18 ms
vt
14 ms
vt
14 ms
vt
14 ms
vt
35 ms
vt
26 ms
vt
19 ms
vt
15 ms
vt
19 ms
vt
15 ms
vt
19 ms
vt
21 ms
vt
30 ms
AuthenticationService.Authenticate
123 ms
4gps.de accessibility score
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
4gps.de 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
Browser errors were logged to the console
4gps.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 4gps.de 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 4gps.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.
4gps.de
Open Graph description is not detected on the main page of 4GPS. 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: