Report Summary

  • 75

    Performance

    Renders faster than
    84% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 78

    SEO

    Google-friendlier than
    40% of websites

coolidge.org

Welcome to the Coolidge Corner Theatre | Coolidge Corner Theater

Page Load Speed

599 ms in total

First Response

16 ms

Resources Loaded

362 ms

Page Rendered

221 ms

coolidge.org screenshot

About Website

Click here to check amazing Coolidge content for United States. Otherwise, check out these important facts you probably never knew about coolidge.org

Visit coolidge.org

Key Findings

We analyzed Coolidge.org page load time and found that the first response time was 16 ms and then it took 583 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

coolidge.org performance score

75

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

43/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.043

99/100

15%

TTI (Time to Interactive)

Value4.9 s

78/100

10%

Network Requests Diagram

coolidge.org

16 ms

www.coolidge.org

44 ms

ddblock-cycle-coolidge-front.css

19 ms

css_271d741fa9feab3b39876f2962845a40.css

53 ms

grid24-960.css

18 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 97% of them (74 requests) were addressed to the original Coolidge.org, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (137 ms) relates to the external source Google-analytics.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 541.9 kB (32%)

Content Size

1.7 MB

After Optimization

1.1 MB

In fact, the total size of Coolidge.org main page is 1.7 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 67.8 kB

  • Original 79.9 kB
  • After minification 68.5 kB
  • After compression 12.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 11.4 kB, which is 14% 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 67.8 kB or 85% of the original size.

Image Optimization

-8%

Potential reduce by 83.9 kB

  • Original 1.1 MB
  • After minification 1.0 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. Coolidge images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 237.2 kB

  • Original 316.5 kB
  • After minification 257.2 kB
  • After compression 79.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 237.2 kB or 75% of the original size.

CSS Optimization

-84%

Potential reduce by 152.9 kB

  • Original 183.0 kB
  • After minification 159.7 kB
  • After compression 30.2 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. Coolidge.org needs all CSS files to be minified and compressed as it can save up to 152.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (61%)

Requests Now

74

After Optimization

29

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

Accessibility Review

coolidge.org accessibility score

88

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Best Practices

coolidge.org best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

coolidge.org SEO score

78

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Coolidge.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Coolidge.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 Coolidge. 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: