7.2 sec in total
94 ms
5 sec
2.1 sec
Click here to check amazing Community Oreilly content for Germany. Otherwise, check out these important facts you probably never knew about community.oreilly.de
IT-Literatur von O'Reilly
Visit community.oreilly.deWe analyzed Community.oreilly.de page load time and found that the first response time was 94 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
community.oreilly.de performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value8.2 s
2/100
25%
Value5.0 s
63/100
10%
Value10 ms
100/100
30%
Value0.006
100/100
15%
Value4.5 s
82/100
10%
94 ms
922 ms
187 ms
277 ms
204 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 53% of them (61 requests) were addressed to the original Community.oreilly.de, 11% (13 requests) were made to Pbs.twimg.com and 9% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Community.oreilly.de.
Page size can be reduced by 446.1 kB (16%)
2.8 MB
2.4 MB
In fact, the total size of Community.oreilly.de main page is 2.8 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. 65% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 73.0 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 73.0 kB or 74% of the original size.
Potential reduce by 90.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. Community Oreilly images are well optimized though.
Potential reduce by 220.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 220.1 kB or 68% of the original size.
Potential reduce by 62.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. Community.oreilly.de needs all CSS files to be minified and compressed as it can save up to 62.5 kB or 83% of the original size.
Number of requests can be reduced by 53 (46%)
114
61
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Community Oreilly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
blog
94 ms
922 ms
style.css
187 ms
shariff.min.local.css
277 ms
wp-syntax.css
204 ms
jquery.js
468 ms
jquery-migrate.min.js
204 ms
shCore.css
276 ms
shThemeDefault.css
276 ms
shCore.js
379 ms
shBrushAS3.js
358 ms
shBrushBash.js
365 ms
shBrushCSharp.js
366 ms
shBrushCpp.js
367 ms
shBrushCss.js
451 ms
shBrushDelphi.js
457 ms
shBrushDiff.js
458 ms
shBrushGroovy.js
459 ms
shBrushJScript.js
495 ms
shBrushJava.js
541 ms
shBrushJavaFX.js
548 ms
shBrushPerl.js
549 ms
shBrushPhp.js
550 ms
shBrushPlain.js
556 ms
shBrushPowerShell.js
569 ms
shBrushPython.js
633 ms
shBrushRuby.js
639 ms
shBrushScala.js
640 ms
shBrushSql.js
641 ms
shBrushVb.js
649 ms
shBrushXml.js
663 ms
wp-emoji-release.min.js
542 ms
wp-embed.min.js
478 ms
shariff.js
661 ms
0673c8118606e6fe6f844224a33fd1cd
69 ms
108d49e21079c77d157fcc08dc52a50f
68 ms
smalldot.gif
105 ms
arrow.gif
99 ms
simple-smile.png
109 ms
markusehrenmueller.jpg
157 ms
sqlsaturdaylogo.png
901 ms
knoff_hoff_android_lesen-253x450.png
980 ms
knoff_hoff_android_hoeren-253x450.png
1260 ms
pocket_liste-253x450.png
900 ms
zweiaufeinemrad-321x450.jpg
876 ms
julia-253x450.png
899 ms
hans_dorsch-150x150.jpg
976 ms
buchandroidtablets2ger.s.gif
980 ms
androidsmartphoquer3ger.s.gif
979 ms
2015-09-10-JavaLand-2016-Banner-1280x640-840x400.jpg
1155 ms
ausstellungshalle.jpg
1342 ms
oreillybuecher.jpg
1343 ms
naorobot.jpg
1644 ms
karussell.jpg
1828 ms
Ruhr_MF_logos_Wordpress-620x126.png
1407 ms
Internet_940x502_300dpi_Ada_17-3-15_lay.jpg
1659 ms
Nadine.jpg
1804 ms
Kalenderbild_Blog.jpg
1630 ms
visualstorytellingger.s.gif
1541 ms
blog-des-jahres-2.gif
1607 ms
piwik.js
1784 ms
dots.gif
1703 ms
widgets.js
15 ms
likebox.php
142 ms
hDvwL1_H7g-.css
25 ms
56WNbrUYLbL.css
29 ms
q68gy-v_YMF.js
663 ms
FJmpeSpHpjS.js
685 ms
0wM5s1Khldu.js
699 ms
1bNoFZUdlYZ.js
698 ms
1f609.png
322 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
113 ms
shariff3uu.woff
873 ms
1487343_10151841431147549_1285086362_n.png
488 ms
1506658_10151841431632549_760947016_n.jpg
511 ms
12417854_1081439978543255_3389425470442109958_n.jpg
544 ms
1919136_10153921494441718_6851920984192277534_n.jpg
522 ms
12642617_10206106588798884_6568756356106891830_n.jpg
529 ms
11013442_1687694238133373_5200768713787455428_n.jpg
599 ms
wL6VQj7Ab77.png
73 ms
s7jcwEQH7Sx.png
72 ms
syndication
114 ms
385075554489098241
361 ms
proxy.jpg
160 ms
1f60a.png
81 ms
13cxIqYGbNNR_kEi.jpg
100 ms
1f60d.png
75 ms
1f4aa.png
75 ms
1f45f.png
74 ms
proxy.jpg
149 ms
proxy.jpg
150 ms
proxy.jpg
149 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
35 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
49 ms
yRAPNEkE_normal.jpeg
108 ms
0RD9Pm5u_normal.jpeg
51 ms
F1d8n6OC_normal.png
119 ms
qYxloNPk_normal.jpg
108 ms
-9r58S4L_normal.jpg
50 ms
-z0IudgC_normal.png
179 ms
CdthxC2UsAAF6oe.jpg:small
52 ms
Cdvm_OSWAAANife.jpg:small
52 ms
CdlvFY2WIAAugyB.jpg:small
118 ms
CdVlFBrW0AEpOt0.jpg:small
104 ms
CdVjsRqWEAAL9vt.jpg:small
119 ms
CdGM6zqW4AAs6lz.jpg:small
133 ms
default_profile_5_normal.png
43 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
51 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
82 ms
I6-MnjEovm5.js
20 ms
pQrUxxo5oQp.js
19 ms
proxy.jpg
31 ms
proxy.jpg
36 ms
proxy.jpg
33 ms
proxy.jpg
42 ms
jot.html
2 ms
community.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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
community.oreilly.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
community.oreilly.de SEO score
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
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Community.oreilly.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 Community.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.
community.oreilly.de
Open Graph data is detected on the main page of Community Oreilly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: