Tools & Wizards About Us
zstime.com screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 42

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

zstime.com

Page Load Speed

44.5 sec in total

First Response

2.1 sec

Resources Loaded

42.1 sec

Page Rendered

299 ms

zstime.com screenshot

About Website

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

厦门尊尚时计贸易有限公司代理的腕表品牌包括并不限于，Daniel Wellington（丹尼尔惠灵顿）、Bering（白令）TORGOEN（托格恩）、abart（爱彼雅）、ZENO（芝诺），ZIIIRO等国际名牌手表。

Visit zstime.com

Key Findings

We analyzed Zstime.com page load time and found that the first response time was 2.1 sec and then it took 42.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 30 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

zstime.com performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value5.9 s

47/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.164

72/100

15%

TTI (Time to Interactive)

Value3.2 s

94/100

10%

Network Requests Diagram

zstime.com

2114 ms

www.zstime.com

18537 ms

bootstrap.min.css

594 ms

common.css

824 ms

fade.css

2073 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 91% of them (48 requests) were addressed to the original Zstime.com, 6% (3 requests) were made to Cdn.bootcss.com and 4% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Zstime.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 133.0 kB (81%)

Content Size

164.0 kB

After Optimization

31.0 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Zstime.com main page is 164.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. 20% of websites need less resources to load. CSS take 109.5 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 18.3 kB

  • Original 22.7 kB
  • After minification 17.3 kB
  • After compression 4.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 5.4 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 18.3 kB or 81% of the original size.

JavaScript Optimization

-73%

Potential reduce by 23.3 kB

  • Original 31.8 kB
  • After minification 31.8 kB
  • After compression 8.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 23.3 kB or 73% of the original size.

CSS Optimization

-83%

Potential reduce by 91.4 kB

  • Original 109.5 kB
  • After minification 109.5 kB
  • After compression 18.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. Zstime.com needs all CSS files to be minified and compressed as it can save up to 91.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (60%)

Requests Now

20

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

zstime.com

zstime.com

2114 ms

www.zstime.com

www.zstime.com

18537 ms

bootstrap.min.css

bootstrap.min.css

594 ms

common.css

common.css

824 ms

fade.css

fade.css

2073 ms

logo.png

logo.png

6717 ms

nav-arrow.png

nav-arrow.png

1255 ms

ico.jpg

ico.jpg

5578 ms

jquery-2.1.1.min.js

jquery-2.1.1.min.js

15050 ms

bootstrap.min.js

bootstrap.min.js

20 ms

target.js

target.js

423 ms

fade.js

fade.js

491 ms

common.js

common.js

828 ms

imgctrl.js

imgctrl.js

835 ms

jquery.lazyload.js

jquery.lazyload.js

2145 ms

gotop.js

gotop.js

1229 ms

ie10-viewport-bug-workaround.js

ie10-viewport-bug-workaround.js

1229 ms

respond.min.js

respond.min.js

1646 ms

bootstrap-ie.js

bootstrap-ie.js

3076 ms

jquery.zoomImgRollover.js

jquery.zoomImgRollover.js

3132 ms

20151014144636_537.jpg

20151014144636_537.jpg

20422 ms

20150706183408_393.jpg

20150706183408_393.jpg

20421 ms

20151013173015_101.jpg

20151013173015_101.jpg

20422 ms

20151014130139_981.jpg

20151014130139_981.jpg

20421 ms

20151014130153_755.jpg

20151014130153_755.jpg

20422 ms

dw.png

dw.png

20422 ms

bering.png

bering.png

20423 ms

triwa.png

triwa.png

20422 ms

komono.png

komono.png

20423 ms

go.png

go.png

20423 ms

xd1.jpg

xd1.jpg

20423 ms

xd2.jpg

xd2.jpg

20422 ms

dd1.jpg

dd1.jpg

20423 ms

dd2.JPG

dd2.JPG

20423 ms

dx3.jpg

dx3.jpg

20423 ms

dx4.jpg

dx4.jpg

20422 ms

dx5.jpg

dx5.jpg

20421 ms

dx6.jpg

dx6.jpg

20422 ms

dd3.jpg

dd3.jpg

20421 ms

welcome.jpg

welcome.jpg

20420 ms

index_line.png

index_line.png

20420 ms

bg.png

bg.png

19997 ms

banner_bg.png

banner_bg.png

19996 ms

h.js

h.js

780 ms

index_block.png

index_block.png

19948 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

61 ms

skin_dw.png

skin_dw.png

19946 ms

bering_mask.png

bering_mask.png

19609 ms

triwa_mask.png

triwa_mask.png

19602 ms

komono_mask.png

komono_mask.png

20194 ms

go_mask.png

go_mask.png

20194 ms

hm.gif

hm.gif

285 ms

weixin.jpg

weixin.jpg

19778 ms

Accessibility Review

zstime.com accessibility score

42

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

zstime.com best practices score

75

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

Browser errors were logged to the console

SEO Factors

zstime.com SEO score

67

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    UTF-8

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

zstime.com

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