Tools & Wizards About Us
iterowatch.com screenshot

Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

iterowatch.com

502 Bad Gateway

Page Load Speed

3.1 sec in total

First Response

245 ms

Resources Loaded

2.4 sec

Page Rendered

403 ms

iterowatch.com screenshot

About Website

Visit iterowatch.com now to see the best up-to-date Iterowatch content and also check out these interesting facts you probably never knew about iterowatch.com

Itero pocket watches are nothing like the old-fashioned pocket watches. With great features, minimalist design and affordable price, they are made for everyone.

Visit iterowatch.com

Key Findings

We analyzed Iterowatch.com page load time and found that the first response time was 245 ms and then it took 2.8 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

iterowatch.com performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

91/100

10%

LCP (Largest Contentful Paint)

Value1.7 s

99/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.7 s

100/100

10%

Network Requests Diagram

iterowatch.com

245 ms

timber.scss.css

118 ms

theme.scss.css

133 ms

css

149 ms

ga_urchin_forms-0826cdefee6590321eb5c0c435eeebf7a8425a5493a9e95059c40e07e069ad52.js

130 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Iterowatch.com, 61% (23 requests) were made to Cdn.shopify.com and 13% (5 requests) were made to S3.amazonaws.com. The less responsive or slowest element that took the longest time to load (864 ms) relates to the external source Cdn.shopify.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 208.8 kB (27%)

Content Size

762.0 kB

After Optimization

553.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Iterowatch.com main page is 762.0 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. 40% of websites need less resources to load. Images take 443.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 26.2 kB

  • Original 31.6 kB
  • After minification 23.8 kB
  • After compression 5.4 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 7.8 kB, which is 25% 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 26.2 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 81 B

  • Original 443.3 kB
  • After minification 443.2 kB

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. Iterowatch images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 93.8 kB

  • Original 179.0 kB
  • After minification 151.6 kB
  • After compression 85.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 93.8 kB or 52% of the original size.

CSS Optimization

-82%

Potential reduce by 88.7 kB

  • Original 108.1 kB
  • After minification 105.6 kB
  • After compression 19.5 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. Iterowatch.com needs all CSS files to be minified and compressed as it can save up to 88.7 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

34

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

iterowatch.com

iterowatch.com

245 ms

timber.scss.css

timber.scss.css

118 ms

theme.scss.css

theme.scss.css

133 ms

css

css

149 ms

ga_urchin_forms-0826cdefee6590321eb5c0c435eeebf7a8425a5493a9e95059c40e07e069ad52.js

ga_urchin_forms-0826cdefee6590321eb5c0c435eeebf7a8425a5493a9e95059c40e07e069ad52.js

130 ms

jquery.min.js

jquery.min.js

159 ms

modernizr.min.js

modernizr.min.js

135 ms

fastclick.min.js

fastclick.min.js

140 ms

timber.js

timber.js

226 ms

theme.js

theme.js

153 ms

slick.min.js

slick.min.js

156 ms

slick-theme.js

slick-theme.js

153 ms

shopify_stats.js

shopify_stats.js

228 ms

analytics.js

analytics.js

241 ms

logo.png

logo.png

194 ms

logo-inverted.png

logo-inverted.png

194 ms

hero_slide_3.jpg

hero_slide_3.jpg

226 ms

Midas_Black_Frontalno_large.jpg

Midas_Black_Frontalno_large.jpg

197 ms

Platinum_Black_Frontalno_large.jpg

Platinum_Black_Frontalno_large.jpg

196 ms

Midnight_Rose_Frontalno_large.jpg

Midnight_Rose_Frontalno_large.jpg

191 ms

Midas_White_Frontalno_large.jpg

Midas_White_Frontalno_large.jpg

206 ms

Platinum_white_Frontalno_large.jpg

Platinum_white_Frontalno_large.jpg

202 ms

Itero_Ambient-3_large.jpg

Itero_Ambient-3_large.jpg

204 ms

Itero_Ambient-2_30d0d6f4-b8f1-43b2-ae56-0961e50b6da5_large.jpg

Itero_Ambient-2_30d0d6f4-b8f1-43b2-ae56-0961e50b6da5_large.jpg

201 ms

ajax-loader.gif

ajax-loader.gif

57 ms

zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf

zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf

55 ms

icons.woff

icons.woff

76 ms

icons.woff

icons.woff

864 ms

collect

collect

35 ms

record.gif

record.gif

105 ms

quickannouncementbar.js

quickannouncementbar.js

94 ms

icf.js

icf.js

98 ms

common.js

common.js

50 ms

common.css

common.css

17 ms

b9b5a60c5c18a427b7a5c53e336de425.css

b9b5a60c5c18a427b7a5c53e336de425.css

46 ms

b9b5a60c5c18a427b7a5c53e336de425.js

b9b5a60c5c18a427b7a5c53e336de425.js

24 ms

cart.js

cart.js

143 ms

qab_get_bar

qab_get_bar

47 ms

Accessibility Review

iterowatch.com accessibility score

95

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

iterowatch.com 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

SEO Factors

iterowatch.com SEO score

75

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iterowatch.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Iterowatch.com 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

iterowatch.com

Open Graph data is detected on the main page of Iterowatch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: