3.9 sec in total
377 ms
3.1 sec
429 ms
Click here to check amazing Ottofond content. Otherwise, check out these important facts you probably never knew about ottofond.de
Visit ottofond.deWe analyzed Ottofond.de page load time and found that the first response time was 377 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
ottofond.de performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value3.8 s
54/100
25%
Value5.9 s
48/100
10%
Value480 ms
60/100
30%
Value0.02
100/100
15%
Value4.0 s
88/100
10%
377 ms
688 ms
605 ms
857 ms
366 ms
Our browser made a total of 35 requests to load all elements on the main page. We found that 71% of them (25 requests) were addressed to the original Ottofond.de, 9% (3 requests) were made to S.ytimg.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Ottofond.de.
Page size can be reduced by 527.0 kB (64%)
817.2 kB
290.1 kB
In fact, the total size of Ottofond.de main page is 817.2 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. 65% of websites need less resources to load. Javascripts take 371.0 kB which makes up the majority of the site volume.
Potential reduce by 13.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. This page needs HTML code to be minified as it can gain 2.7 kB, which is 15% 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 13.8 kB or 76% of the original size.
Potential reduce by 25.7 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. Obviously, Ottofond needs image optimization as it can save up to 25.7 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 254.4 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 254.4 kB or 69% of the original size.
Potential reduce by 233.2 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. Ottofond.de needs all CSS files to be minified and compressed as it can save up to 233.2 kB or 83% of the original size.
Number of requests can be reduced by 9 (29%)
31
22
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ottofond. 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.
ottofond.de
377 ms
www.ottofond.de
688 ms
ottofond.css
605 ms
prototype.js
857 ms
lytebox.css
366 ms
lytebox.js
612 ms
fluidvids.min.js
246 ms
ticker.js
352 ms
script.js
491 ms
bg.jpg
1363 ms
blau_1px.jpg
152 ms
header_bg.png
189 ms
logo-bg.png
190 ms
logo_small.png
689 ms
header_foto.png
694 ms
lang-en-off.gif
315 ms
Lupe_klein_button.jpg
690 ms
mobileBtn.png
690 ms
unten_links.jpg
690 ms
button_menue-links.jpg
691 ms
Galia%20II%20Mod.%20A%20mit%20TU1000_deko.jpg
721 ms
box_titel.jpg
691 ms
box.jpg
703 ms
box_unten.jpg
691 ms
aufzaehlung.jpg
702 ms
Vy5BFTg_Vx8
82 ms
ga.js
12 ms
__utm.gif
40 ms
www-embed-player-vfl-z2BtK.css
50 ms
www-embed-player.js
109 ms
base.js
170 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
98 ms
ad_status.js
269 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
205 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
211 ms
ottofond.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
ottofond.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
ottofond.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
DE
DE
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ottofond.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 Ottofond.de main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
ottofond.de
Open Graph description is not detected on the main page of Ottofond. 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: