4.8 sec in total
939 ms
3 sec
870 ms
Click here to check amazing Oelzrezepte content. Otherwise, check out these important facts you probably never knew about oelzrezepte.com
Das Familienunternehmen Rudolf Ölz Meisterbäcker GmbH & Co KG ist führend in der Herstellung von Backwaren. Dabei haben Tradition & Innovation Priorität.
Visit oelzrezepte.comWe analyzed Oelzrezepte.com page load time and found that the first response time was 939 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
oelzrezepte.com performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value3.3 s
70/100
25%
Value9.4 s
12/100
10%
Value6,420 ms
0/100
30%
Value0.968
2/100
15%
Value16.1 s
6/100
10%
939 ms
56 ms
199 ms
195 ms
332 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Oelzrezepte.com, 4% (2 requests) were made to Fast.fonts.net and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Oelz.com.
Page size can be reduced by 396.0 kB (11%)
3.5 MB
3.1 MB
In fact, the total size of Oelzrezepte.com main page is 3.5 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 3.1 MB which makes up the majority of the site volume.
Potential reduce by 66.1 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 25.5 kB, which is 34% 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 66.1 kB or 89% of the original size.
Potential reduce by 35.8 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. Oelzrezepte images are well optimized though.
Potential reduce by 199.5 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 199.5 kB or 68% of the original size.
Potential reduce by 94.6 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. Oelzrezepte.com needs all CSS files to be minified and compressed as it can save up to 94.6 kB or 84% of the original size.
Number of requests can be reduced by 3 (6%)
54
51
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oelzrezepte. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
939 ms
655c912d-4961-4530-b452-cb2381cf5c15.css
56 ms
style.css
199 ms
modernizr-2.5.3.min.js
195 ms
jquery-1.11.3.min.js
332 ms
script.min.js
333 ms
logo-oelz-header.png
296 ms
header_1400x365px_300dpi_oelz_riesen_toast_erdaepfelkaes-1.jpg
577 ms
header_1400x365px_300dpi_oelzriesen_toast_lachstartar.jpg
535 ms
header_1400x365px_300dpi_oelzriesen_toast_honigtopfenzimtapfel.jpg
570 ms
header_scheiterhaufenoelzbutterbrioche-1.jpg
575 ms
gradient-header.png
493 ms
wave-up.png
392 ms
thomas_dorfer_portrait.jpg
491 ms
o--lz-riesen-toast_0002_oelz_riesentoast_riesen_french_toast.jpg
685 ms
header_1400x365px_300dpi_oelzriesen_toast_honigtopfenzimtapfel.jpg
702 ms
o--lz-riesen-french-toast.jpg
631 ms
header_1400x365px_300dpi_oelzriesen_toast_lachstartar.jpg
671 ms
oelz_punsch_stollen_0001.jpg
675 ms
oelz_edel_marzipan_stollen.jpg
678 ms
oelz_butter_mandel_stollen.jpg
730 ms
butter_christ_stollen.jpg
777 ms
header_rezept_td_nuss-strudel-terrine.jpg
771 ms
header_rezept_td_marmormurmeln.jpg
783 ms
amaretto_brombeeren_schnitten.jpg
790 ms
maracuja_mango_toertchen-2.jpg
798 ms
header_oelzkraeuterbuttertoast_barbecuestyle_1400x365px_300dpi_r.jpg
828 ms
oelzkraeuterbuttertoast_bueffelmozzarella_parmaschinken_1400x365.jpg
869 ms
oelz_kraeuterbuttertoastmitrindspaillard_1400x365px_300dpi_rgb.jpg
879 ms
header_scheiterhaufenoelzbutterbrioche-1.jpg
882 ms
header_dinkelzopfsauerrahmschmarrn-1.jpg
990 ms
header_suesseroelzbutterbriocheauflauf-1.jpg
896 ms
header_300dp_doerrobspofesen-1.jpg
924 ms
header_cremevonderbutterbrioche-1.jpg
965 ms
header_oelzkornspitztoast_rotepfeffercreme_bresaola_1400x365px_3.jpg
982 ms
header_oelzkornspitztoast_doerrzwetschkencreme_1400x365px_300dpi.jpg
985 ms
oelz-mehrkorn-toast.jpg
1093 ms
oelztoast_11_092_a.jpg
1022 ms
oelzmehrkorntoast_entenbrust__12_099_a.jpg
1063 ms
lz-mehrkorn-toast-mit-ruccola-schafkaese--ofenpaprika-und-serran.jpg
1027 ms
oelzsanwdichtoast_caesarsalad_13_132_a.jpg
1010 ms
analytics.js
50 ms
oelz-sandwich-toast-mit-eierschwammerl-cottage-cheese-und-putenschinken-.jpg
1039 ms
6a88c79d-0905-4fcd-ab00-31ea72f717f3.woff
58 ms
collect
12 ms
cgcollag-webfont.woff
835 ms
Oelz.ttf
874 ms
cgcollab-webfont.woff
699 ms
cgcollai-webfont.woff
732 ms
oelztoast_8_060_a.jpg
694 ms
oelz-butter-toast.jpg
694 ms
toast.png
914 ms
toaster.png
917 ms
wave-up-color-bright.png
669 ms
logo-oelz-footer.png
636 ms
ajax-loader.gif
648 ms
oelzrezepte.com 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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
oelzrezepte.com 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
oelzrezepte.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Document doesn't have a valid hreflang
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 Oelzrezepte.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 Oelzrezepte.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.
oelzrezepte.com
Open Graph description is not detected on the main page of Oelzrezepte. 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: