6 sec in total
298 ms
5.2 sec
445 ms
Welcome to rodenstock-blog.com homepage info - get ready to check Rodenstock Blog best content right away, or after learning these important things about rodenstock-blog.com
Mit dem Rodenstock Journal möchten wir unsere Begeisterung und unser Know-how weitergeben und Sie über aktuelle News, Produkte, Highlights und Trends rund um die Brille informieren.
Visit rodenstock-blog.comWe analyzed Rodenstock-blog.com page load time and found that the first response time was 298 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
rodenstock-blog.com performance score
298 ms
3813 ms
380 ms
193 ms
9 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 68% of them (38 requests) were addressed to the original Rodenstock-blog.com, 13% (7 requests) were made to Facebook.com and 7% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Rodenstock-blog.com.
Page size can be reduced by 149.9 kB (22%)
667.7 kB
517.7 kB
In fact, the total size of Rodenstock-blog.com main page is 667.7 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. 35% of websites need less resources to load. Images take 468.4 kB which makes up the majority of the site volume.
Potential reduce by 45.6 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 45.6 kB or 81% of the original size.
Potential reduce by 21.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. Rodenstock Blog images are well optimized though.
Potential reduce by 55.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 55.7 kB or 50% of the original size.
Potential reduce by 27.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. Rodenstock-blog.com needs all CSS files to be minified and compressed as it can save up to 27.1 kB or 84% of the original size.
Number of requests can be reduced by 23 (43%)
54
31
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rodenstock Blog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
rodenstock-blog.com
298 ms
www.rodenstock-blog.com
3813 ms
style.css
380 ms
front.css
193 ms
jquery.min.js
9 ms
external-tracking.min.js
194 ms
analytics.js
21 ms
shdw_general_left.png
192 ms
987x210_BE-RELAXED.jpg
478 ms
bgr_main_nav.jpg
202 ms
en.gif
192 ms
es.gif
196 ms
Woodlook_Blog.jpg
700 ms
link.gif
384 ms
Bogner2016_520x250.png
1141 ms
ErgoBlog_2-520x251.jpg
673 ms
Unbenannt.jpg
854 ms
USA-PreRace-11-blog_-520x250.jpg
1043 ms
pagination.gif
865 ms
collect
13 ms
sidebar.gif
117 ms
roden-house.png
192 ms
external.gif
193 ms
rss_on.gif
197 ms
rss.gif
198 ms
facebook_on.gif
285 ms
facebook.gif
379 ms
twitter_on.gif
379 ms
twitter.gif
381 ms
youtube_on.gif
383 ms
youtube.gif
384 ms
instagram_sw.png
472 ms
instagram.png
565 ms
social-label.gif
566 ms
social-selected.gif
567 ms
all.js
9 ms
rodblog-2-40-40.jpg
491 ms
default.jpg
27 ms
142 ms
xd_arbiter.php
38 ms
xd_arbiter.php
52 ms
jquery.validate.js
660 ms
common.js
561 ms
front.js
560 ms
shdw_general_right.png
561 ms
jquery-ui.custom.min.js
747 ms
ga.js
57 ms
__utm.gif
19 ms
like.php
96 ms
like.php
110 ms
like.php
110 ms
like.php
134 ms
like.php
127 ms
like.php
138 ms
qeKvIRsJabD.js
26 ms
LVx-xkvaJ0b.png
15 ms
rodenstock-blog.com SEO score
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rodenstock-blog.com 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 Rodenstock-blog.com 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.
rodenstock-blog.com
Open Graph description is not detected on the main page of Rodenstock Blog. 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: