5 sec in total
1.3 sec
3.2 sec
542 ms
Click here to check amazing Osterloh content. Otherwise, check out these important facts you probably never knew about osterloh.org
Visit osterloh.orgWe analyzed Osterloh.org page load time and found that the first response time was 1.3 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
osterloh.org performance score
name
value
score
weighting
Value8.5 s
0/100
10%
Value13.7 s
0/100
25%
Value14.1 s
1/100
10%
Value90 ms
99/100
30%
Value0
100/100
15%
Value12.4 s
15/100
10%
1253 ms
234 ms
469 ms
502 ms
218 ms
Our browser made a total of 33 requests to load all elements on the main page. We found that 73% of them (24 requests) were addressed to the original Osterloh.org, 24% (8 requests) were made to Use.typekit.net and 3% (1 request) were made to P.typekit.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Osterloh.org.
Page size can be reduced by 285.3 kB (11%)
2.5 MB
2.2 MB
In fact, the total size of Osterloh.org main page is 2.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. 45% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 10.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. 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 10.5 kB or 69% of the original size.
Potential reduce by 1.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. Osterloh images are well optimized though.
Potential reduce by 201.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 201.5 kB or 70% of the original size.
Potential reduce by 71.5 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. Osterloh.org needs all CSS files to be minified and compressed as it can save up to 71.5 kB or 89% of the original size.
Number of requests can be reduced by 10 (38%)
26
16
The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Osterloh. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
1253 ms
xpp7tkj.js
234 ms
layout.css
469 ms
jquery.js
502 ms
jquery-migrate.min.js
218 ms
underscore.min.js
165 ms
leaflet.js
584 ms
osterloh-map.min.js
202 ms
osterloh-gallery.min.js
224 ms
osterloh-inline-gallery.min.js
251 ms
osterloh.min.js
307 ms
wp-embed.min.js
327 ms
wp-emoji-release.min.js
289 ms
www.osterloh.org
96 ms
01_hero-s.jpg
820 ms
pattern-blue.jpg
300 ms
02-1_teaser-termine-s.jpg
756 ms
placeholder-quad.png
105 ms
IMG_7398.jpg
437 ms
02-2_teaser-erleben-s.jpg
692 ms
10_teaser-team-s.jpg
563 ms
IMG_7636-1.jpg
979 ms
wb8jDigijSFyA01fuZqNgjaBAN1HMjsSEsecVxSJQ09ffOezgsMdeMJ6Mk6g5Msfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
30 ms
TgMnWVtrRx8MnCBj03bZ7Ob3SCo9mPL25TcaxxRZD0IffHrzgsMdeMJ6Mk6g5Mmfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
62 ms
3y_185qKAkYAG1ABWr9mOTKBnUhnZDtAEZHwqnEFcCjffHczgsMdeMJ6Mk6g5Mifb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
91 ms
playfairdisplay-regular-webfont.woff
527 ms
ostercon.svg
656 ms
ostercon.woff
651 ms
playfairdisplay-italic-webfont.woff
757 ms
p.gif
113 ms
nNpVRCrbu2vyV6k-KOXAvPUe3W3h8Gj15_gQlKK7PtSffOHzgsMdeMJ6Mk6g5Mofb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
33 ms
gb3hZ9eCRCXO4uPYFdEhaHK-DbMFHlxFD9Mow6X3H4bffOfzgsMdeMJ6Mk6g5MNfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
32 ms
YAlJJjBqtw3hFVnCeVKfDIK7W-shX-SOGiTWBsPauIGffH7zgsMdeMJ6Mk6g5gBfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
33 ms
osterloh.org accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
[id] attributes on active, focusable elements are not unique
osterloh.org 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
osterloh.org 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Osterloh.org can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Osterloh.org 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.
osterloh.org
Open Graph description is not detected on the main page of Osterloh. 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: