2.8 sec in total
315 ms
2.3 sec
220 ms
Visit oreilly.de now to see the best up-to-date O Reilly content for Germany and also check out these interesting facts you probably never knew about oreilly.de
KI & Machine Learning, Programmierung, Webdev, Data Science, Marketing und Business: Bücher von O'Reilly liefern Praxiswissen.
Visit oreilly.deWe analyzed Oreilly.de page load time and found that the first response time was 315 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
oreilly.de performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value5.1 s
24/100
25%
Value9.2 s
13/100
10%
Value320 ms
77/100
30%
Value0.346
32/100
15%
Value12.7 s
13/100
10%
315 ms
343 ms
96 ms
50 ms
190 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 93% of them (54 requests) were addressed to the original Oreilly.de, 3% (2 requests) were made to Community.oreilly.de and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Community.oreilly.de.
Page size can be reduced by 119.8 kB (59%)
201.6 kB
81.8 kB
In fact, the total size of Oreilly.de main page is 201.6 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. Only 10% of websites need less resources to load. Javascripts take 64.3 kB which makes up the majority of the site volume.
Potential reduce by 24.4 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 24.4 kB or 73% of the original size.
Potential reduce by 11.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. Obviously, O Reilly needs image optimization as it can save up to 11.6 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 43.1 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 43.1 kB or 67% of the original size.
Potential reduce by 40.7 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. Oreilly.de needs all CSS files to be minified and compressed as it can save up to 40.7 kB or 82% of the original size.
Number of requests can be reduced by 10 (18%)
55
45
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of O Reilly. 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.
oreilly.de
315 ms
343 ms
all.css
96 ms
jquery.min.js
50 ms
engine.js
190 ms
common.js
190 ms
home.css
218 ms
gplus-16.png
36 ms
uf_unbesucht.gif
121 ms
uf_besucht.gif
118 ms
haendlerbanner1.gif
114 ms
haendlerbanner2.gif
124 ms
minecraftbuchger_xs.gif
212 ms
spotifybuchger_xs.gif
214 ms
buchandroidtablets2ger-xs.gif
223 ms
phoenixprojectger_xs.gif
226 ms
durchstartenswift2ger_xs.gif
219 ms
praxvmwarevs6ger_xs.gif
230 ms
lichtundspassger_xs.gif
305 ms
elektronikprojekteger_xs.gif
310 ms
joomlabuchger_xs.gif
317 ms
pwwordpress4ger_xs.gif
319 ms
angularjsger_xs.gif
323 ms
hfjavascriptprogger_xs.gif
329 ms
androidseniorenger_xs.gif
402 ms
office2016ger_xs.gif
408 ms
datenanalysemitpythonger_xs.gif
413 ms
effectivemodcplusger_xs.gif
421 ms
facebookprogger_xs.gif
428 ms
visualstorytellingger_xs.gif
432 ms
newcommrules4ger_xs.gif
499 ms
userstorymapger_xs.gif
503 ms
startupownerger_xs.gif
509 ms
googleanalyticsger_xs.gif
516 ms
technischseoger_xs.gif
521 ms
ecommerceger_xs.gif
526 ms
email-16x16.gif
587 ms
feed-icon-16x16.png
592 ms
blog_icon.png
599 ms
twitter-16x16.png
606 ms
facebook-16x16.png
612 ms
elekraspberrybasger_xs.gif
618 ms
ipadseniorenger_xs.gif
682 ms
piwik.js
1123 ms
elekarduinobas2ger_xs.gif
674 ms
joomla3ger_xs.gif
595 ms
androidsmartphoquer3ger_xs.gif
601 ms
wenschleprogger_xs.gif
603 ms
facebookbucheltern2ger_xs.gif
607 ms
storytellingger_xs.gif
584 ms
progspasskidsger_xs.gif
588 ms
home_tarsier.jpg
699 ms
oreilly_large.gif
603 ms
button_cart.gif
601 ms
bg_nav.gif
598 ms
box-item-header.gif
585 ms
bullet_menu.gif
583 ms
piwik.js
285 ms
oreilly.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
Image elements do not have [alt] attributes
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.
oreilly.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
oreilly.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oreilly.de 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 Oreilly.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.
oreilly.de
Open Graph description is not detected on the main page of O Reilly. 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: