4.4 sec in total
1.1 sec
2.1 sec
1.2 sec
Click here to check amazing Mainz content for Germany. Otherwise, check out these important facts you probably never knew about mainz.de
Die Gutenberg- und Medienstadt stellt sich vor. Mit Informationen aus dem Rathaus, über das Leben in Mainz, über das touristische Angebot und Freizeitangebote.
Visit mainz.deWe analyzed Mainz.de page load time and found that the first response time was 1.1 sec and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
mainz.de performance score
name
value
score
weighting
Value7.4 s
1/100
10%
Value7.6 s
3/100
25%
Value7.4 s
28/100
10%
Value0 ms
100/100
30%
Value0.034
100/100
15%
Value7.4 s
48/100
10%
1111 ms
826 ms
315 ms
211 ms
216 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 95% of them (39 requests) were addressed to the original Mainz.de, 2% (1 request) were made to and 2% (1 request) were made to Mz-piwik.sitepark.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Mainz.de.
Page size can be reduced by 359.8 kB (28%)
1.3 MB
931.5 kB
In fact, the total size of Mainz.de main page is 1.3 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. 40% of websites need less resources to load. Images take 881.6 kB which makes up the majority of the site volume.
Potential reduce by 86.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 35.9 kB, which is 36% 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 86.5 kB or 88% of the original size.
Potential reduce by 18.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. Mainz images are well optimized though.
Potential reduce by 27.7 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 27.7 kB or 65% of the original size.
Potential reduce by 227.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. Mainz.de needs all CSS files to be minified and compressed as it can save up to 227.4 kB or 85% of the original size.
Number of requests can be reduced by 4 (18%)
22
18
The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mainz. 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 CSS and as a result speed up the page load time.
mainz.de
1111 ms
stylesheet.css
826 ms
icon.css
315 ms
navigation.css
211 ms
sp-site-api.css
216 ms
sp-site-api.js
318 ms
modernizr.custom.15312.js
316 ms
jquery-1.11.2.js
975 ms
jquery.mobile.custom.js
624 ms
Toggle.js
412 ms
Navigation.js
415 ms
Table.js
518 ms
jquery.sitepark.accordion.js
522 ms
jquery.sitepark.tabs.js
623 ms
TabsAccordionSwitcher.js
629 ms
jquery.sitepark.website.js
725 ms
OffCanvas.js
727 ms
Grid.js
732 ms
navigation.js
861 ms
jquery.solr.js
860 ms
javascript.js
861 ms
Slideshow.js
861 ms
logo.png
141 ms
gAAACMAAAAAACMAABAAAAAAAAAAAAAAAAAAAAOAAAAAAAAAAAAAAAAAEAAAACAAAAAgAAJQIAAAACAAAAAgAAAAIAACsCAAArAgAAAAIAAC8CAAALAgAALwIAAC8CAAAAAgAAAAIAAE8CAAA5AgAAAAIAABcCAAAAAgAAAgIAAC0CAAAVAgAAUAIAAGACAAANAgAAAwIAAAACAAAaAgAAAAIAABcCAAANAgAAFwIAAAUCAAAqAgAABgIAAC8CAAApAgAAAAIAAAACAAAAAgAAAAIAAAACIAAAAiAAcAIAAAACMAAAAgAAQAIAAAACAAAEAiAAAAIAAGICAAApAAAAAAAKABQAHgBQAF4AtgEGARoBLgFCAVYBiAG6AewCGgIsApoC7AMqA4oDrgSaBQQFbAWyBeAGDAccB0QHWAe4B8YH9gg4CJII4gmICgAKcArMDGYMsA0KDTINdA28DhYOXA6wDsYO+A9oEAYQVBCCAAAAAQAAADgBMQARAAAAAAACAAAAAAAAAAAAAAAAAAAAAAAAAA4ArgABAAAAAAABABwAAAABAAAAAAACAA4AeAABAAAAAAADABwAMgABAAAAAAAEABwAhgABAAAAAAAFABYAHAABAAAAAAAGAA4ATgABAAAAAAAKADQAogADAAEECQABABwAAAADAAEECQACAA4AeAADAAEECQADABwAMgADAAEECQAEABwAhgADAAEECQAFABYAHAADAAEECQAGABwAXAADAAEECQAKADQAogBTAFAALQBpAGMAbwBuAHMALQBtAGEAaQBuAHoAVgBlAHIAcwBpAG8AbgAgADEALgAwAFMAUAAtAGkAYwBvAG4AcwAtAG0AYQBpAG4AelNQLWljb25zLW1haW56AFMAUAAtAGkAYwBvAG4AcwAtAG0AYQBpAG4AegBSAGUAZwB1AGwAYQByAFMAUAAtAGkAYwBvAG4AcwAtAG0AYQBpAG4AegBGAG8AbgB0ACAAZwBlAG4AZQByAGEAdABlAGQAIABiAHkAIABJAGMAbwBNAG8AbwBuAC4AAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
22 ms
990x300.pm2.bgFFFFFF.jpg
209 ms
990x300.pm2.bgFFFFFF.jpg
312 ms
990x300.pm2.bgFFFFFF.jpg
212 ms
990x300.pm2.bgFFFFFF.jpg
520 ms
990x300.pm2.bgFFFFFF.jpg
414 ms
990x300.pm2.bgFFFFFF.jpg
398 ms
990x300.pm2.bgFFFFFF.jpg
412 ms
296x198.pm2.bgFFFFFF.jpg
315 ms
296x198.pm2.bgFFFFFF.jpg
415 ms
296x198.pm2.bgFFFFFF.jpg
421 ms
296x198.pm2.bgFFFFFF.jpg
501 ms
169x75.pm0.bgFFFFFF.jpg
515 ms
371x77.pm0.bgFFFFFF.png
515 ms
176x77.pm0.bgFFFFFF.png
515 ms
176x77.pm0.bgFFFFFF.png
520 ms
piwik.js
541 ms
stylesheet-print.css
106 ms
mainz.de accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
mainz.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
mainz.de 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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mainz.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 Mainz.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.
mainz.de
Open Graph data is detected on the main page of Mainz. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: