Tools & Wizards About Us
watch110.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

watch110.com

گالری ساعت ۱۱۰ | نمایندگی ساعت سیتیزن | ساعت سیتیزن اصل | قیمت ساعت سیتیزن

Page Load Speed

9.7 sec in total

First Response

2.3 sec

Resources Loaded

7.2 sec

Page Rendered

203 ms

watch110.com screenshot

About Website

Click here to check amazing Watch 110 content for Iran. Otherwise, check out these important facts you probably never knew about watch110.com

گالری ساعت ۱۱۰ (مجتبی نجد) ، نمایندگی ساعت سیتیزن ژاپن ، با نزدیک به نیم قرن سابقه ، در بازار بزرگ تهران کار خود را آغاز نمود .

Visit watch110.com

Key Findings

We analyzed Watch110.com page load time and found that the first response time was 2.3 sec and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

watch110.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value14.6 s

1/100

10%

TBT (Total Blocking Time)

Value960 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.82

4/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

www.watch110.com

2273 ms

autoptimize_9d0b1eb43697d5529e69a4b60de20cfc.css

648 ms

autoptimize_eece99974ec2cd2b04c281b7111b7197.css

218 ms

autoptimize_single_36ea4805809e6b690c2f5126a0808297.css

216 ms

jquery.js

324 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 77% of them (17 requests) were addressed to the original Watch110.com, 18% (4 requests) were made to Maps.googleapis.com and 5% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Watch110.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 142.6 kB (11%)

Content Size

1.4 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 28.2 kB

  • Original 35.9 kB
  • After minification 35.9 kB
  • After compression 7.7 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 28.2 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 2.1 kB

  • Original 676.5 kB
  • After minification 674.4 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. Watch 110 images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 56.0 kB

  • Original 417.5 kB
  • After minification 417.5 kB
  • After compression 361.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 56.0 kB or 13% of the original size.

CSS Optimization

-25%

Potential reduce by 56.4 kB

  • Original 226.4 kB
  • After minification 226.4 kB
  • After compression 170.1 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. Watch110.com needs all CSS files to be minified and compressed as it can save up to 56.4 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (44%)

Requests Now

18

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.watch110.com

www.watch110.com

2273 ms

autoptimize_9d0b1eb43697d5529e69a4b60de20cfc.css

autoptimize_9d0b1eb43697d5529e69a4b60de20cfc.css

648 ms

autoptimize_eece99974ec2cd2b04c281b7111b7197.css

autoptimize_eece99974ec2cd2b04c281b7111b7197.css

218 ms

autoptimize_single_36ea4805809e6b690c2f5126a0808297.css

autoptimize_single_36ea4805809e6b690c2f5126a0808297.css

216 ms

jquery.js

jquery.js

324 ms

autoptimize_81a62213b603aaa4ec7bf6dede1dd16c.js

autoptimize_81a62213b603aaa4ec7bf6dede1dd16c.js

863 ms

cropped-Citizen110.png

cropped-Citizen110.png

301 ms

slider-1.jpg

slider-1.jpg

302 ms

slider-2-1.jpg

slider-2-1.jpg

457 ms

slider-3.jpg

slider-3.jpg

401 ms

citizen-automatic-watch.png

citizen-automatic-watch.png

584 ms

024952852bm698351h.jpg

024952852bm698351h.jpg

301 ms

embed

embed

280 ms

iryekan.woff

iryekan.woff

373 ms

Defaults.woff

Defaults.woff

235 ms

skin.css

skin.css

120 ms

wild-sea2.png

wild-sea2.png

133 ms

js

js

34 ms

search.js

search.js

5 ms

geometry.js

geometry.js

9 ms

main.js

main.js

22 ms

Simple-Line-Icons.ttf

Simple-Line-Icons.ttf

117 ms

Accessibility Review

watch110.com accessibility score

81

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

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

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

watch110.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

watch110.com SEO score

100

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

Language and Encoding

  • Language Detected

    FA

  • Language Claimed

    FA

  • Encoding

    UTF-8

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

watch110.com

Open Graph description is not detected on the main page of Watch 110. 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: