Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

daytimer.ca

Day-Timer Personal & Professional Planners, Organizers & Refills

Page Load Speed

2.4 sec in total

First Response

208 ms

Resources Loaded

1.9 sec

Page Rendered

258 ms

daytimer.ca screenshot

About Website

Click here to check amazing Day Timer content for Canada. Otherwise, check out these important facts you probably never knew about daytimer.ca

Day Planner Organizers with leather covers are prefect for any professional or individual with busy schedules. Day-Timer offers the best selection of refillable planners!

Visit daytimer.ca

Key Findings

We analyzed Daytimer.ca page load time and found that the first response time was 208 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

daytimer.ca performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value3,360 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.094

91/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

www.daytimer.ca

208 ms

www.daytimer.ca

358 ms

355 ms

otSDKStub.js

60 ms

DYTsite.css

133 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 7% of them (2 requests) were addressed to the original Daytimer.ca, 60% (18 requests) were made to Daytimer.com and 10% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (394 ms) relates to the external source Daytimer.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 120.2 kB (21%)

Content Size

571.3 kB

After Optimization

451.0 kB

In fact, the total size of Daytimer.ca main page is 571.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Javascripts take 399.5 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 69.3 kB

  • Original 82.5 kB
  • After minification 62.9 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 19.6 kB, which is 24% 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 69.3 kB or 84% of the original size.

JavaScript Optimization

-5%

Potential reduce by 21.3 kB

  • Original 399.5 kB
  • After minification 399.5 kB
  • After compression 378.3 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

-33%

Potential reduce by 29.6 kB

  • Original 89.2 kB
  • After minification 89.2 kB
  • After compression 59.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. Daytimer.ca needs all CSS files to be minified and compressed as it can save up to 29.6 kB or 33% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (48%)

Requests Now

21

After Optimization

11

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

Accessibility Review

daytimer.ca accessibility score

98

Accessibility Issues

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

daytimer.ca best practices score

83

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

daytimer.ca SEO score

98

Search Engine Optimization Advices

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