Access tim.oreilly.com. O'Reilly Media - Technology and Business Training

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value2,370 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.0 s

4/100

10%

tim.oreilly.com

196 ms

464 ms

jquery.min.js

56 ms

stylesheet.css

35 ms

nav.css

31 ms

Our browser made a total of 131 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Tim.oreilly.com, 15% (19 requests) were made to Cdn.oreillystatic.com and 8% (10 requests) were made to Channel9.msdn.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Channel9.msdn.com.

Content Size

2.0 MB

After Optimization

648.6 kB

In fact, the total size of Tim.oreilly.com main page is 2.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 955.5 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 72.9 kB

Original 101.1 kB
After minification 95.1 kB
After compression 28.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. 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 72.9 kB or 72% of the original size.

Image Optimization

-3%

Potential reduce by 2.3 kB

Original 93.5 kB
After minification 91.1 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. Tim O Reilly images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 585.7 kB

Original 955.5 kB
After minification 936.8 kB
After compression 369.7 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 585.7 kB or 61% of the original size.

CSS Optimization

-80%

Potential reduce by 652.4 kB

Original 812.0 kB
After minification 789.4 kB
After compression 159.6 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. Tim.oreilly.com needs all CSS files to be minified and compressed as it can save up to 652.4 kB or 80% of the original size.

Requests Now

126

After Optimization

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

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

Links do not have descriptive text

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Tim.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 Tim.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

tim.oreilly.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

O'Reilly Media - Technology and Business Training

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

tim.oreilly.com

jquery.min.js

stylesheet.css

nav.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

tim.oreilly.com

jquery.min.js

stylesheet.css

nav.css

mbstyles.css

mybuys3.js

setup.js

s_code.js

all-post-ml.css

ml.css

ml.js

bmj2nsh.js

oreilly.css

about.css

tim.css

login-config.js

janrain-settings.js

login-widget.min.js

ml-libraries.css

ml-grids.css

ml-content.css

ml-special.css

footerScripts.js

utilities.js

datasource-min.js

autocomplete-min.js

autocomplete_data.js

plusone.js

ga.js

j.php

w.js

load.js

ml-header-about.png

INC_Cover_sm.jpg

publishing-point-frame.jpg

basketicon.gif

search_btn.gif

tim-2010.jpg

social-icons-16.png

s32654058374464

v.gif

social-icons.gif

29052688

25753372