Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 70

    SEO

    Google-friendlier than
    29% of websites

timex.ca

Watches from Timex | Digital, Analog, & Water Resistant Watches

Page Load Speed

8.1 sec in total

First Response

208 ms

Resources Loaded

6.1 sec

Page Rendered

1.8 sec

timex.ca screenshot

About Website

Welcome to timex.ca homepage info - get ready to check Timex best content for Canada right away, or after learning these important things about timex.ca

Timex offers a suite of watches for men, women, boys, and girls. Shop watches now and get free shipping on orders over $75. Shop Timex watches today!

Visit timex.ca

Key Findings

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

Performance Metrics

timex.ca performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value12.1 s

3/100

10%

TBT (Total Blocking Time)

Value4,400 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.372

28/100

15%

TTI (Time to Interactive)

Value30.0 s

0/100

10%

Network Requests Diagram

timex.ca

208 ms

www.timex.ca

375 ms

rapid.min.6.1.6.js

287 ms

header-plugins.js

148 ms

persistent.css

152 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 24% of them (28 requests) were addressed to the original Timex.ca, 27% (32 requests) were made to Images.timex.com and 25% (30 requests) were made to Flowcdn.io. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Timex.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 279.5 kB (12%)

Content Size

2.3 MB

After Optimization

2.0 MB

In fact, the total size of Timex.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.6 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 159.6 kB

  • Original 193.6 kB
  • After minification 193.5 kB
  • After compression 34.0 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 159.6 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 11.5 kB

  • Original 1.6 MB
  • After minification 1.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. Timex images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 79.2 kB

  • Original 300.3 kB
  • After minification 255.0 kB
  • After compression 221.1 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 79.2 kB or 26% of the original size.

CSS Optimization

-16%

Potential reduce by 29.2 kB

  • Original 187.8 kB
  • After minification 186.4 kB
  • After compression 158.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. Timex.ca needs all CSS files to be minified and compressed as it can save up to 29.2 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (32%)

Requests Now

111

After Optimization

75

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

Accessibility Review

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

button, link, and menuitem elements do not have accessible names.

High

ARIA input fields do not have accessible names

High

ARIA IDs are not unique

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

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

Best Practices

timex.ca best practices score

67

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

timex.ca 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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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 Timex.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 Timex.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 description is not detected on the main page of Timex. 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: