Tools & Wizards About Us
post.oreilly.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

post.oreilly.com

O'Reilly Media - Technology and Business Training

Page Load Speed

1.2 sec in total

First Response

263 ms

Resources Loaded

633 ms

Page Rendered

296 ms

post.oreilly.com screenshot

About Website

Visit post.oreilly.com now to see the best up-to-date Post O Reilly content for India and also check out these interesting facts you probably never knew about post.oreilly.com

Gain technology and business knowledge and hone your skills with learning resources created and curated by O'Reilly's experts: live online training, video, books, our platform has content from 200+ of...

Visit post.oreilly.com

Key Findings

We analyzed Post.oreilly.com page load time and found that the first response time was 263 ms and then it took 929 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

post.oreilly.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

18/100

25%

SI (Speed Index)

Value4.1 s

80/100

10%

TBT (Total Blocking Time)

Value980 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.231

54/100

15%

TTI (Time to Interactive)

Value13.0 s

13/100

10%

Network Requests Diagram

post.oreilly.com

263 ms

www.oreilly.com

31 ms

jquery.min.js

32 ms

stylesheet.css

22 ms

nav.css

20 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Post.oreilly.com, 43% (38 requests) were made to Cdn.oreillystatic.com and 14% (12 requests) were made to Akamaicovers.oreilly.com. The less responsive or slowest element that took the longest time to load (263 ms) belongs to the original domain Post.oreilly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 428.0 kB (42%)

Content Size

1.0 MB

After Optimization

599.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Post.oreilly.com main page is 1.0 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 449.7 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 89.5 kB

  • Original 107.7 kB
  • After minification 91.1 kB
  • After compression 18.2 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 16.6 kB, which is 15% 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 89.5 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 874 B

  • Original 449.7 kB
  • After minification 448.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. Post O Reilly images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 148.5 kB

  • Original 246.4 kB
  • After minification 228.8 kB
  • After compression 97.9 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 148.5 kB or 60% of the original size.

CSS Optimization

-85%

Potential reduce by 189.1 kB

  • Original 223.1 kB
  • After minification 204.5 kB
  • After compression 34.0 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. Post.oreilly.com needs all CSS files to be minified and compressed as it can save up to 189.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (60%)

Requests Now

86

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Post 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 28 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

post.oreilly.com

post.oreilly.com

263 ms

www.oreilly.com

www.oreilly.com

31 ms

jquery.min.js

jquery.min.js

32 ms

stylesheet.css

stylesheet.css

22 ms

nav.css

nav.css

20 ms

mbstyles.css

mbstyles.css

15 ms

mybuys3.js

mybuys3.js

14 ms

setup.js

setup.js

13 ms

s_code.js

s_code.js

22 ms

ml.css

ml.css

17 ms

ml.js

ml.js

17 ms

bmj2nsh.js

bmj2nsh.js

101 ms

oreilly.css

oreilly.css

10 ms

login-config.js

login-config.js

10 ms

janrain-settings.js

janrain-settings.js

9 ms

login-widget.min.js

login-widget.min.js

14 ms

jquery-ui.min.js

jquery-ui.min.js

60 ms

pwr-full.js

pwr-full.js

13 ms

footerScripts.js

footerScripts.js

13 ms

utilities.js

utilities.js

57 ms

datasource-min.js

datasource-min.js

55 ms

autocomplete-min.js

autocomplete-min.js

55 ms

autocomplete_data.js

autocomplete_data.js

205 ms

ml-libraries.css

ml-libraries.css

10 ms

ml-grids.css

ml-grids.css

9 ms

ml-content.css

ml-content.css

14 ms

ml-special.css

ml-special.css

16 ms

bkt.gif

bkt.gif

88 ms

bkt.gif

bkt.gif

88 ms

thumb.gif

thumb.gif

88 ms

ml-header-home-blinking.gif

ml-header-home-blinking.gif

18 ms

basketicon.gif

basketicon.gif

18 ms

large-search.png

large-search.png

18 ms

ba-fluent16-20160115.png

ba-fluent16-20160115.png

85 ms

ba-lp-prep-for-cissp-cert-domains1-4_20160217.jpg

ba-lp-prep-for-cissp-cert-domains1-4_20160217.jpg

33 ms

ba-strata16-20160120.jpg

ba-strata16-20160120.jpg

36 ms

sean_suchter-50.jpg

sean_suchter-50.jpg

20 ms

andy-petrella-300x300.jpg

andy-petrella-300x300.jpg

22 ms

xavier-tordoir-300x300.jpg

xavier-tordoir-300x300.jpg

22 ms

jesse-anderson-300x300.jpg

jesse-anderson-300x300.jpg

33 ms

jonathan-stark-300x300.jpg

jonathan-stark-300x300.jpg

28 ms

katherine-hague-300x300.jpg

katherine-hague-300x300.jpg

34 ms

safari-logo-202x68.png

safari-logo-202x68.png

35 ms

ga.js

ga.js

39 ms

j.php

j.php

33 ms

load.js

load.js

32 ms

btn-green-arrow-overlay.png

btn-green-arrow-overlay.png

46 ms

pr_styles_review.css

pr_styles_review.css

44 ms

reviews_social.css

reviews_social.css

38 ms

contents.js

contents.js

43 ms

social-icons-16.png

social-icons-16.png

40 ms

bullet-disc.png

bullet-disc.png

41 ms

item-list-nav-bg.png

item-list-nav-bg.png

39 ms

btn-green-arrow-overlay.png

btn-green-arrow-overlay.png

40 ms

jessica-mckellar-160x180-20150715.jpg

jessica-mckellar-160x180-20150715.jpg

40 ms

v.gif

v.gif

32 ms

login.oreilly.com

login.oreilly.com

36 ms

__utm.gif

__utm.gif

40 ms

s26947335144504

s26947335144504

63 ms

contents.js

contents.js

24 ms

contents.js

contents.js

23 ms

social-icons.gif

social-icons.gif

25 ms

wr.do

wr.do

48 ms

capture:login

capture:login

11 ms

chartbeat.js

chartbeat.js

42 ms

sso.js

sso.js

100 ms

providers.css

providers.css

27 ms

ping

ping

45 ms

item-list-left-bg.png

item-list-left-bg.png

45 ms

thumb.gif

thumb.gif

35 ms

item-list-left-arrow.png

item-list-left-arrow.png

27 ms

item-list-right-bg.png

item-list-right-bg.png

28 ms

item-list-right-arrow.png

item-list-right-arrow.png

27 ms

item-list-scroll-bg.png

item-list-scroll-bg.png

25 ms

item-list-scroll-handle.png

item-list-scroll-handle.png

27 ms

rc_thumb.gif

rc_thumb.gif

17 ms

thumb.gif

thumb.gif

12 ms

thumb.gif

thumb.gif

16 ms

thumb.gif

thumb.gif

16 ms

thumb.gif

thumb.gif

11 ms

thumb.gif

thumb.gif

18 ms

rc_thumb.gif

rc_thumb.gif

18 ms

thumb.gif

thumb.gif

24 ms

thumb.gif

thumb.gif

23 ms

thumb.gif

thumb.gif

24 ms

rc_thumb.gif

rc_thumb.gif

24 ms

6381.js

6381.js

23 ms

6381.js

6381.js

16 ms

Accessibility Review

post.oreilly.com accessibility score

90

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

ARIA IDs are not unique

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

Low

No form fields have multiple labels

Best Practices

post.oreilly.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

post.oreilly.com SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Post.oreilly.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Post.oreilly.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.

Social Sharing Optimization

post.oreilly.com

Open Graph description is not detected on the main page of Post 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: