9.5 sec in total
1.1 sec
8 sec
391 ms
Click here to check amazing Orthy content. Otherwise, check out these important facts you probably never knew about orthy.de
Bloggen, was läuft!
Visit orthy.deWe analyzed Orthy.de page load time and found that the first response time was 1.1 sec and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
orthy.de performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value8.9 s
1/100
25%
Value7.7 s
25/100
10%
Value480 ms
60/100
30%
Value0.089
92/100
15%
Value8.4 s
39/100
10%
1104 ms
323 ms
225 ms
330 ms
312 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 58% of them (26 requests) were addressed to the original Orthy.de, 11% (5 requests) were made to I0.wp.com and 9% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source I2.wp.com.
Page size can be reduced by 511.5 kB (70%)
734.7 kB
223.2 kB
In fact, the total size of Orthy.de main page is 734.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. 30% of websites need less resources to load. Javascripts take 395.4 kB which makes up the majority of the site volume.
Potential reduce by 35.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. 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 35.1 kB or 78% of the original size.
Potential reduce by 0 B
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. Orthy images are well optimized though.
Potential reduce by 285.6 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 285.6 kB or 72% of the original size.
Potential reduce by 190.8 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. Orthy.de needs all CSS files to be minified and compressed as it can save up to 190.8 kB or 81% of the original size.
Number of requests can be reduced by 28 (72%)
39
11
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Orthy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.orthy.de
1104 ms
wp-emoji-release.min.js
323 ms
twentyfifteen.css
225 ms
mediaelementplayer.min.css
330 ms
wp-mediaelement.css
312 ms
css
59 ms
genericons.css
353 ms
style.css
244 ms
twentyfifteen.css
345 ms
jetpack.css
371 ms
jquery.js
651 ms
jquery-migrate.min.js
458 ms
spin.js
398 ms
jquery.spin.js
406 ms
tiled-gallery.js
420 ms
infinity.js
371 ms
jquery.cycle.js
524 ms
slideshow-shortcode.js
516 ms
photon.js
468 ms
devicepx-jetpack.js
5 ms
jetpack-carousel.js
474 ms
mediaelement-and-player.min.js
598 ms
wp-mediaelement.js
596 ms
gprofiles.js
58 ms
wpgroho.js
597 ms
skip-link-focus-fix.js
662 ms
functions.js
678 ms
wp-embed.min.js
680 ms
e-201611.js
3 ms
f4-tex.jpg
735 ms
3fragezeichen.png
1363 ms
palm.png
972 ms
dvsd.png
486 ms
snake2.png
784 ms
strandeddeep.png
1010 ms
endlich.png
27 ms
fVu1p3782bqS2z-CaJvp9i3USBnSvpkopQaUR-2r7iU.ttf
38 ms
lJAvZoKA5NttpPc9yc6lPbOLyRJkM5aLlPlkJMOAyH0.ttf
57 ms
PIbvSEyHEdL91QLOQRnZ19qQynqKV_9Plp7mupa0S4g.ttf
64 ms
erE3KsIWUumgD1j_Ca-V-6CWcynf_cDxXwCLxiixG1c.ttf
65 ms
Genericons.svg
366 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
9 ms
hovercard.css
29 ms
services.css
54 ms
g.gif
3 ms
orthy.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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
orthy.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
orthy.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 Orthy.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 Orthy.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.
orthy.de
Open Graph data is detected on the main page of Orthy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: