3.5 sec in total
322 ms
2.9 sec
307 ms
Click here to check amazing Rostock content for Germany. Otherwise, check out these important facts you probably never knew about rostock.de
Herzlich Willkommen in der Hansestadt Rostock. Urlaub ✓ Lifestyle ✓ Kultur ✓ Aktivitäten ✓ Historisches ✓ Maritimes. Entdecken Sie Rostock
Visit rostock.deWe analyzed Rostock.de page load time and found that the first response time was 322 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
rostock.de performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value4.5 s
37/100
25%
Value6.9 s
34/100
10%
Value1,150 ms
22/100
30%
Value0
100/100
15%
Value10.2 s
25/100
10%
322 ms
710 ms
210 ms
217 ms
428 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 68% of them (39 requests) were addressed to the original Rostock.de, 12% (7 requests) were made to Lib.lupcom.net and 11% (6 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (912 ms) belongs to the original domain Rostock.de.
Page size can be reduced by 881.9 kB (43%)
2.0 MB
1.2 MB
In fact, the total size of Rostock.de main page is 2.0 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 936.6 kB which makes up the majority of the site volume.
Potential reduce by 84.3 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 16.0 kB, which is 16% 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 84.3 kB or 84% of the original size.
Potential reduce by 44.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. Rostock images are well optimized though.
Potential reduce by 445.8 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 445.8 kB or 71% of the original size.
Potential reduce by 307.0 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. Rostock.de needs all CSS files to be minified and compressed as it can save up to 307.0 kB or 83% of the original size.
Number of requests can be reduced by 25 (47%)
53
28
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rostock. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
rostock.de
322 ms
www.rostock.de
710 ms
nivo-slider.css
210 ms
jquery.mCustomScrollbar.css
217 ms
bootstrap.min.css
428 ms
jquery.fancybox.css
319 ms
jquery-ui.css
322 ms
daterangepicker.css
218 ms
2b1926dc9f57.css
328 ms
require.js
220 ms
jquery.nivo.slider.pack.js
120 ms
logo-hansestadt-458x90-neu.png
117 ms
ktg-rostock-navigationsbanner.jpg
540 ms
Kommune%20des%20Jahres%20Navigationsbanner%20263%20x%20328.jpg
224 ms
rathaus-stadtverwaltung-344352b2.jpg
224 ms
eisbaer-fiete-zoo-rostock.jpg
110 ms
flughafen-rostock-laage.jpg
223 ms
segeln-zum-greifen.jpg
332 ms
leben-wohnen.jpg
332 ms
bildung-wissenschaft.jpg
441 ms
rathaus.jpg
336 ms
banner-rostock-ist.jpg
440 ms
wiro-desktop.jpg
743 ms
wiro-tablet.jpg
645 ms
wiro-mobil.jpg
554 ms
stadthalle-messehalle-desktop.jpg
772 ms
stadthalle-messehalle-tablet.jpg
657 ms
stadthalle-messehalle-mobil.jpg
648 ms
lup-footer-logo-hansestadt-rostock.png
664 ms
videohandler.v5.min.js
728 ms
icon-hotel-aktiv.png
744 ms
icon-fewo-haus.png
745 ms
icon-pension.png
752 ms
icon-faehre.png
825 ms
jquery.min.js
335 ms
footer-silhouette.png
824 ms
cse.js
16 ms
analytics.js
41 ms
daterangepicker.js
831 ms
moment.min.js
837 ms
main20160208.min.js
832 ms
popup.min.js
860 ms
rostock_nav.min.js
912 ms
cse.js
149 ms
collect
13 ms
jsapi
38 ms
default+de.css
8 ms
default.css
20 ms
default+de.I.js
23 ms
default.css
29 ms
async-ads.js
89 ms
small-logo.png
25 ms
jquery.mCustomScrollbar.concat.min.js
583 ms
bootstrap.min.js
219 ms
stadthafen-min.jpg
323 ms
jquery.fancybox.pack.js
220 ms
jquery-ui.min.js
557 ms
rostock.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
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.
rostock.de 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
rostock.de 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
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 Rostock.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 Rostock.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.
rostock.de
Open Graph data is detected on the main page of Rostock. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: