Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

cambridgetimes.ca

Cambridge, Ontario News | Cambridge Times

Page Load Speed

2.6 sec in total

First Response

98 ms

Resources Loaded

1.7 sec

Page Rendered

776 ms

cambridgetimes.ca screenshot

About Website

Visit cambridgetimes.ca now to see the best up-to-date Cambridge Times content for Canada and also check out these interesting facts you probably never knew about cambridgetimes.ca

Stay informed with the latest news updates from the Cambridge Times website. Breaking news, top stories, politics, business, sports, & more.

Visit cambridgetimes.ca

Key Findings

We analyzed Cambridgetimes.ca page load time and found that the first response time was 98 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

cambridgetimes.ca performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value13.0 s

0/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value4,430 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value27.4 s

0/100

10%

Network Requests Diagram

cambridgetimes.ca

98 ms

www.cambridgetimes.ca

191 ms

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

87 ms

layout.5bce7eb56c23d79d6ab89ab093c281ea.css

111 ms

oovvuu.css

98 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 6% of them (7 requests) were addressed to the original Cambridgetimes.ca, 56% (60 requests) were made to Bloximages.chicago2.vip.townnews.com and 6% (7 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (575 ms) relates to the external source Bloximages.chicago2.vip.townnews.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 470.5 kB (20%)

Content Size

2.3 MB

After Optimization

1.8 MB

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

HTML Optimization

-89%

Potential reduce by 426.5 kB

  • Original 476.8 kB
  • After minification 410.7 kB
  • After compression 50.3 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 66.2 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 426.5 kB or 89% of the original size.

Image Optimization

-1%

Potential reduce by 8.8 kB

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

JavaScript Optimization

-3%

Potential reduce by 23.5 kB

  • Original 678.0 kB
  • After minification 678.0 kB
  • After compression 654.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. This website has mostly compressed JavaScripts.

CSS Optimization

-19%

Potential reduce by 11.6 kB

  • Original 60.0 kB
  • After minification 60.0 kB
  • After compression 48.4 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. Cambridgetimes.ca needs all CSS files to be minified and compressed as it can save up to 11.6 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 50 (49%)

Requests Now

103

After Optimization

53

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

Accessibility Review

cambridgetimes.ca accessibility score

77

Accessibility Issues

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

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

Impact

Issue

High

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

Best Practices

cambridgetimes.ca best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

cambridgetimes.ca SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 Cambridgetimes.ca 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 Cambridgetimes.ca 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 Cambridge Times. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: