Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 70

    SEO

    Google-friendlier than
    30% of websites

cupblog.org

Columbia University Press Blog - Publishing a universe of knowledge for readers worldwide

Page Load Speed

13.1 sec in total

First Response

1.1 sec

Resources Loaded

7.4 sec

Page Rendered

4.6 sec

cupblog.org screenshot

About Website

Welcome to cupblog.org homepage info - get ready to check Cup Blog best content for Italy right away, or after learning these important things about cupblog.org

Publishing a universe of knowledge for readers worldwide

Visit cupblog.org

Key Findings

We analyzed Cupblog.org page load time and found that the first response time was 1.1 sec and then it took 12 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

cupblog.org performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value5,390 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

www.cupblog.org

1142 ms

embed.js

38 ms

style.css

16 ms

sharethis.js

6 ms

sharethis.1ac33bc7d4476110a610f925104446ff.css

11 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 5% of them (5 requests) were addressed to the original Cupblog.org, 16% (15 requests) were made to E1a780df6a2327e24485-d73868e25b2d2bf91c2b7fd7417bb2e3.r15.cf2.rackcdn.com and 9% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Cupblog.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 744.5 kB (16%)

Content Size

4.6 MB

After Optimization

3.9 MB

In fact, the total size of Cupblog.org main page is 4.6 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. Images take 3.7 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 102.7 kB

  • Original 136.5 kB
  • After minification 133.9 kB
  • After compression 33.9 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 102.7 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 65.0 kB

  • Original 3.7 MB
  • After minification 3.6 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. Cup Blog images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 364.3 kB

  • Original 538.8 kB
  • After minification 538.7 kB
  • After compression 174.5 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 364.3 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 212.6 kB

  • Original 256.5 kB
  • After minification 252.5 kB
  • After compression 44.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. Cupblog.org needs all CSS files to be minified and compressed as it can save up to 212.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (39%)

Requests Now

77

After Optimization

47

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

Accessibility Review

cupblog.org accessibility score

97

Accessibility Issues

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

High

Document doesn't have a <title> element

Best Practices

cupblog.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

cupblog.org SEO score

70

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

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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 Cupblog.org 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 Cupblog.org 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 description is not detected on the main page of Cup Blog. 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: