4.9 sec in total
1 sec
3.3 sec
629 ms
Visit gerlitz.net now to see the best up-to-date Gerlitz content and also check out these interesting facts you probably never knew about gerlitz.net
Visit gerlitz.netWe analyzed Gerlitz.net page load time and found that the first response time was 1 sec and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
gerlitz.net performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value8.0 s
2/100
25%
Value15.5 s
0/100
10%
Value480 ms
60/100
30%
Value0.025
100/100
15%
Value14.2 s
9/100
10%
1018 ms
155 ms
106 ms
140 ms
136 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 55% of them (52 requests) were addressed to the original Gerlitz.net, 13% (12 requests) were made to Maps.googleapis.com and 12% (11 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Gerlitz.net.
Page size can be reduced by 947.8 kB (37%)
2.6 MB
1.6 MB
In fact, the total size of Gerlitz.net main page is 2.6 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 1.3 MB which makes up the majority of the site volume.
Potential reduce by 25.9 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 25.9 kB or 79% of the original size.
Potential reduce by 37.9 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. Gerlitz images are well optimized though.
Potential reduce by 716.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 716.1 kB or 71% of the original size.
Potential reduce by 167.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. Gerlitz.net needs all CSS files to be minified and compressed as it can save up to 167.9 kB or 83% of the original size.
Number of requests can be reduced by 31 (37%)
84
53
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gerlitz. 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 9 to 1 for CSS and as a result speed up the page load time.
www.gerlitz.net
1018 ms
wp-emoji-release.min.js
155 ms
reset.css
106 ms
bootstrap.min.css
140 ms
style.css
136 ms
style-responsive.css
98 ms
prettyPhoto.css
151 ms
font-awesome.min.css
156 ms
oxygen.css
186 ms
jquery.js
269 ms
jquery-migrate.min.js
213 ms
bootstrap.min.js
126 ms
jquery.prettyPhoto.js
91 ms
jquery.form.js
100 ms
jquery.validate.js
111 ms
jquery.inview.js
136 ms
filterable.js
224 ms
jquery.flexslider.js
225 ms
common.js
225 ms
wp-embed.min.js
226 ms
css
37 ms
video_backup.jpg
293 ms
section-background.jpg
166 ms
link-icon.png
156 ms
zoom-icon.png
156 ms
logo-rrh-ramstein-390x280.png
156 ms
external-link.png
154 ms
logo-breit-sachverst%C3%A4ndiger-390x280.png
175 ms
logo-borussia-nk-390x280.png
175 ms
conergy-zweibr%C3%BCcken-390x280.jpg
235 ms
uks-freunde-390x280.jpg
159 ms
industra-390x280.jpg
231 ms
berthold-jung-390x280.jpg
217 ms
fundr-390x280.jpg
257 ms
drk-390x280.jpg
230 ms
white-iphone.png
484 ms
gallery-2-250x190.jpg
264 ms
gallery-3-250x190.jpg
279 ms
gallery-4-250x190.jpg
281 ms
gallery-1-250x190.jpg
282 ms
twitter.png
318 ms
facebook.png
321 ms
google.png
325 ms
linkedin.png
329 ms
pinterest.png
326 ms
dribble.png
369 ms
flickr.png
370 ms
vimeo.png
376 ms
youtube.png
371 ms
forrst.png
381 ms
rss.png
413 ms
arrow-totop.png
422 ms
ensconce-logo.png
152 ms
f8OBjBbevvywgbyJOxlO7Q.ttf
22 ms
AwBqWF2kjhlybWamaKMPcaCWcynf_cDxXwCLxiixG1c.ttf
50 ms
yVHpdQrmTj9Kax1tmFSx2qCWcynf_cDxXwCLxiixG1c.ttf
49 ms
fontawesome-webfont.woff
322 ms
maps
69 ms
embed
573 ms
js
76 ms
init_embed.js
40 ms
common.js
48 ms
map.js
60 ms
google4.png
69 ms
overlay.js
26 ms
util.js
87 ms
onion.js
83 ms
search_impl.js
85 ms
StaticMapService.GetMapImage
263 ms
stats.js
85 ms
openhand_8_8.cur
57 ms
ViewportInfoService.GetViewportInfo
94 ms
ViewportInfoService.GetViewportInfo
89 ms
kh
132 ms
transparent.png
83 ms
controls.js
16 ms
css
79 ms
entity11.png
45 ms
mapcnt6.png
26 ms
vt
120 ms
vt
116 ms
vt
112 ms
vt
108 ms
vt
113 ms
vt
105 ms
vt
149 ms
vt
159 ms
vt
154 ms
vt
150 ms
tmapctrl.png
18 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
27 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
35 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
35 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
35 ms
gerlitz.net 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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
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.
gerlitz.net 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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
gerlitz.net 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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gerlitz.net 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 Gerlitz.net 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.
gerlitz.net
Open Graph description is not detected on the main page of Gerlitz. 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: