Tools & Wizards About Us
hi1718.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 43

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

hi1718.com

Page Load Speed

49.1 sec in total

First Response

1.4 sec

Resources Loaded

47.2 sec

Page Rendered

559 ms

hi1718.com screenshot

About Website

Welcome to hi1718.com homepage info - get ready to check Hi 1718 best content for China right away, or after learning these important things about hi1718.com

捷配仪器仪表网致力于为中国仪器仪表行业企业进行更精准的网络宣传和推广，为广大企业搭建功能全面的网上营销平台，提供丰富、权威的行业资讯，促进行业人士之间的交流，使整个产业链的各个环节的沟通贸易简单，节省企业的营销和物流成本

Visit hi1718.com

Key Findings

We analyzed Hi1718.com page load time and found that the first response time was 1.4 sec and then it took 47.7 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 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

hi1718.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

hi1718.com

1383 ms

www.hi1718.com

10476 ms

newindex.css

6498 ms

jquery-1.4.2.min.js

19584 ms

index.js

1502 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 13% of them (6 requests) were addressed to the original Hi1718.com, 68% (32 requests) were made to File.hi1718.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source File.hi1718.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 190.7 kB (58%)

Content Size

326.0 kB

After Optimization

135.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hi1718.com main page is 326.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. HTML takes 194.6 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 164.2 kB

  • Original 194.6 kB
  • After minification 144.6 kB
  • After compression 30.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 49.9 kB, which is 26% 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 164.2 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 4.1 kB

  • Original 81.4 kB
  • After minification 77.3 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. Hi 1718 images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 8.4 kB

  • Original 32.2 kB
  • After minification 32.2 kB
  • After compression 23.8 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 8.4 kB or 26% of the original size.

CSS Optimization

-78%

Potential reduce by 14.0 kB

  • Original 17.9 kB
  • After minification 15.6 kB
  • After compression 3.9 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. Hi1718.com needs all CSS files to be minified and compressed as it can save up to 14.0 kB or 78% of the original size.

Requests Breakdown

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

Requests Now

43

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hi 1718. 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 as a result speed up the page load time.

Network Requests Diagram

hi1718.com

hi1718.com

1383 ms

www.hi1718.com

www.hi1718.com

10476 ms

newindex.css

newindex.css

6498 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

19584 ms

index.js

index.js

1502 ms

stat.aspx

stat.aspx

8702 ms

safe.jpg

safe.jpg

3462 ms

safe.gif

safe.gif

389 ms

base.png

base.png

2005 ms

201631517145613.gif

201631517145613.gif

7012 ms

201622915292775.gif

201622915292775.gif

1875 ms

201552710244196.gif

201552710244196.gif

1919 ms

titbg.png

titbg.png

1492 ms

iconnew.png

iconnew.png

2488 ms

20139493356922.jpg

20139493356922.jpg

5310 ms

2013991130277.jpg

2013991130277.jpg

13993 ms

2015821102737941.jpg

2015821102737941.jpg

7433 ms

201582495359733.jpg

201582495359733.jpg

12975 ms

201551311135134.gif

201551311135134.gif

7911 ms

201431217392483.gif

201431217392483.gif

7671 ms

2014227143410859.gif

2014227143410859.gif

9274 ms

4.gif

4.gif

9626 ms

3.gif

3.gif

8044 ms

2016322152624438.jpg

2016322152624438.jpg

8916 ms

201632215186938.jpg

201632215186938.jpg

8833 ms

20151023154720832.jpg

20151023154720832.jpg

9270 ms

20151023101932894.jpg

20151023101932894.jpg

9425 ms

20142211651343s.gif

20142211651343s.gif

10972 ms

201472516190360s.jpg

201472516190360s.jpg

10219 ms

2014530152857988s.jpg

2014530152857988s.jpg

20496 ms

2014530153053941s.jpg

2014530153053941s.jpg

10589 ms

2014530153129581s.jpg

2014530153129581s.jpg

11922 ms

pa2.gif

pa2.gif

11064 ms

msn.gif

msn.gif

11338 ms

indexRight.gif

indexRight.gif

11613 ms

425x65_CMEMS_CN.jpg

425x65_CMEMS_CN.jpg

373 ms

ga.js

ga.js

101 ms

__utm.gif

__utm.gif

14 ms

h.js

h.js

3278 ms

s.js

s.js

1290 ms

push.js

push.js

630 ms

hm.gif

hm.gif

377 ms

grey.gif

grey.gif

381 ms

2014321143755548.gif

2014321143755548.gif

12044 ms

20157141510906.gif

20157141510906.gif

20477 ms

20151121516264.gif

20151121516264.gif

14018 ms

nopic1.gif

nopic1.gif

345 ms

Accessibility Review

hi1718.com accessibility score

43

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

Image elements do not have [alt] attributes

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

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

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

hi1718.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

hi1718.com SEO score

92

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

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 uses legible font sizes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hi1718.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Hi1718.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

hi1718.com

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