Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

chronicle.com

The Chronicle of Higher Education | Higher Ed News, Opinion & Advice

Page Load Speed

44.8 sec in total

First Response

250 ms

Resources Loaded

15.6 sec

Page Rendered

29 sec

chronicle.com screenshot

About Website

Visit chronicle.com now to see the best up-to-date Chronicle content for United States and also check out these interesting facts you probably never knew about chronicle.com

In-depth and breaking news, opinion, advice and jobs for professors, deans and others in higher education from The Chronicle of Higher Education.

Visit chronicle.com

Key Findings

We analyzed Chronicle.com page load time and found that the first response time was 250 ms and then it took 44.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

chronicle.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value3,820 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

www.chronicle.com

250 ms

theme.min.css

228 ms

jquery-1.11.2.min.js

835 ms

satelliteLib-b4ea57f8645e2fd6f49369090cf3e4c7b3a4e170.js

180 ms

bootstrap.min.js

801 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 81% of them (46 requests) were addressed to the original Chronicle.com, 4% (2 requests) were made to Assets.adobedtm.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source Securepubads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (22%)

Content Size

6.8 MB

After Optimization

5.4 MB

In fact, the total size of Chronicle.com main page is 6.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. 80% 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. Images take 5.2 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 85.0 kB

  • Original 98.2 kB
  • After minification 63.5 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 34.7 kB, which is 35% 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 85.0 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 327.6 kB

  • Original 5.2 MB
  • After minification 4.9 MB

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. Chronicle images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 850.3 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 429.2 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 850.3 kB or 66% of the original size.

CSS Optimization

-86%

Potential reduce by 230.7 kB

  • Original 268.4 kB
  • After minification 268.1 kB
  • After compression 37.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. Chronicle.com needs all CSS files to be minified and compressed as it can save up to 230.7 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (24%)

Requests Now

46

After Optimization

35

The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Chronicle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

chronicle.com accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

High

Missing source maps for large first-party JavaScript

SEO Factors

chronicle.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

Open Graph data is detected on the main page of Chronicle. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: