Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 62

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

app17.com

阿仪网-仪器信息网,仪器仪表专业平台

Page Load Speed

56.5 sec in total

First Response

2.1 sec

Resources Loaded

53.7 sec

Page Rendered

714 ms

app17.com screenshot

About Website

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

阿仪网致力于为采购商更容易找自己仪器仪表产品信息,仪器仪表企业网络宣传和推广更有效,平台提供实验仪器,化工仪器,分析仪器,光学仪器,无损检测,物理仪器,环境检测,色谱仪器,生物检测,温度仪表,压力 仪表,流量仪表,电工仪表,量具量等产品,权威的行业资讯,促进行业人士之间的交流及交易,节省企业的营销和物流成本。

Visit app17.com

Key Findings

We analyzed App17.com page load time and found that the first response time was 2.1 sec and then it took 54.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 10 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

app17.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.7 s

0/100

25%

SI (Speed Index)

Value14.8 s

1/100

10%

TBT (Total Blocking Time)

Value240 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0.111

87/100

15%

TTI (Time to Interactive)

Value13.4 s

12/100

10%

Network Requests Diagram

app17.com

2075 ms

www.app17.com

12613 ms

common.ashx

696 ms

Industry.IndustryAction,Industry.ashx

766 ms

kefu2015.css

903 ms

Our browser made a total of 180 requests to load all elements on the main page. We found that 34% of them (62 requests) were addressed to the original App17.com, 53% (95 requests) were made to Img1.app17.com and 8% (14 requests) were made to Bdimg.share.baidu.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Img1.app17.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 563.8 kB (53%)

Content Size

1.1 MB

After Optimization

502.5 kB

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

HTML Optimization

-87%

Potential reduce by 379.7 kB

  • Original 436.3 kB
  • After minification 385.5 kB
  • After compression 56.6 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 50.8 kB, which is 12% 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 379.7 kB or 87% of the original size.

Image Optimization

-12%

Potential reduce by 49.0 kB

  • Original 395.3 kB
  • After minification 346.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. Obviously, App 17 needs image optimization as it can save up to 49.0 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-53%

Potential reduce by 103.5 kB

  • Original 195.7 kB
  • After minification 187.6 kB
  • After compression 92.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 103.5 kB or 53% of the original size.

CSS Optimization

-81%

Potential reduce by 31.5 kB

  • Original 39.1 kB
  • After minification 34.6 kB
  • After compression 7.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. App17.com needs all CSS files to be minified and compressed as it can save up to 31.5 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (20%)

Requests Now

168

After Optimization

134

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

Accessibility Review

app17.com accessibility score

52

Accessibility Issues

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

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

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

app17.com best practices score

62

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

app17.com SEO score

83

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise App17.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 App17.com main page’s claimed encoding is gb2312. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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