Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

qiye-163.com

网易企业邮箱-企业信息化专业解决方案-苏州宇腾网络信息技术服务有限公司

Page Load Speed

26.4 sec in total

First Response

1 sec

Resources Loaded

24.7 sec

Page Rendered

679 ms

About Website

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

网易企业邮箱,最安全最稳定,业界第1反垃圾技术,收发速度最快,18年运营经验,1500人专业团队,40万家企业信赖,24小时服务热线:400-400-9010-163。

Visit qiye-163.com

Key Findings

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

Performance Metrics

qiye-163.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

39/100

25%

SI (Speed Index)

Value24.1 s

0/100

10%

TBT (Total Blocking Time)

Value450 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

qiye-163.com

1021 ms

swiper.min.css

221 ms

css.css

426 ms

screen.css

425 ms

jquery.min.js

730 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 96% of them (85 requests) were addressed to the original Qiye-163.com, 2% (2 requests) were made to Hm.baidu.com and 1% (1 request) were made to Goutong.baidu.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Qiye-163.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 466.3 kB (12%)

Content Size

4.0 MB

After Optimization

3.5 MB

In fact, the total size of Qiye-163.com main page is 4.0 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. 25% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 45.7 kB

  • Original 55.2 kB
  • After minification 41.0 kB
  • After compression 9.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 14.2 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 45.7 kB or 83% of the original size.

Image Optimization

-12%

Potential reduce by 415.8 kB

  • Original 3.6 MB
  • After minification 3.2 MB

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, Qiye 163 needs image optimization as it can save up to 415.8 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

-1%

Potential reduce by 3.4 kB

  • Original 320.5 kB
  • After minification 320.5 kB
  • After compression 317.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 1.4 kB

  • Original 19.6 kB
  • After minification 19.6 kB
  • After compression 18.3 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. Qiye-163.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 13 (16%)

Requests Now

79

After Optimization

66

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

Accessibility Review

qiye-163.com accessibility score

73

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.

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

qiye-163.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

Page has valid source maps

SEO Factors

qiye-163.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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qiye-163.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 Qiye-163.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

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