Tools & Wizards About Us
138z.com screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 43

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

138z.com

温州亿速科技有限公司|温州服务器|机柜租用|CDN加速|主机租用|主机托管|服务器|虚拟主机|网站建设|网站空间|企业邮局|域名注册|网站策划|网通托管|温州网通_温州亿速科技有限公司

Page Load Speed

47 sec in total

First Response

4.2 sec

Resources Loaded

42.6 sec

Page Rendered

203 ms

138z.com screenshot

About Website

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

温州亿速科技有限公司倾力于互联网信息服务、电子商务服务等高新技术工作,亿速科技拥有全国领先的网络带宽资源、电子商务方案解决实力,相信我们,重在优质,信誉第一!

Visit 138z.com

Key Findings

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

Performance Metrics

138z.com performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

42/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.253

49/100

15%

TTI (Time to Interactive)

Value4.5 s

82/100

10%

Network Requests Diagram

138z.com

4189 ms

style.css

1296 ms

TMpng.js

8453 ms

sk.js

4101 ms

yu.js

20186 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 83% of them (30 requests) were addressed to the original 138z.com, 8% (3 requests) were made to Pub.idqqimg.com and 3% (1 request) were made to 1.138z.com. The less responsive or slowest element that took the longest time to load (20.2 sec) belongs to the original domain 138z.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 29.5 kB (73%)

Content Size

40.2 kB

After Optimization

10.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 138z.com main page is 40.2 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. HTML takes 16.2 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 11.9 kB

  • Original 16.2 kB
  • After minification 13.5 kB
  • After compression 4.4 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 2.7 kB, which is 17% 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 11.9 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 487 B
  • After minification 487 B

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. 138 Z images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 9.6 kB

  • Original 13.9 kB
  • After minification 13.1 kB
  • After compression 4.3 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 9.6 kB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 8.0 kB

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

Requests Breakdown

Number of requests can be reduced by 10 (42%)

Requests Now

24

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

138z.com

138z.com

4189 ms

style.css

style.css

1296 ms

TMpng.js

TMpng.js

8453 ms

sk.js

sk.js

4101 ms

yu.js

yu.js

20186 ms

tb.js

tb.js

1829 ms

homeapply.aspx

homeapply.aspx

17181 ms

online.ww

online.ww

4099 ms

mainBg.gif

mainBg.gif

491 ms

01.gif

01.gif

2890 ms

q1.gif

q1.gif

525 ms

q2.gif

q2.gif

3875 ms

w1.gif

w1.gif

1045 ms

w2.gif

w2.gif

1064 ms

w3.gif

w3.gif

3037 ms

w4.gif

w4.gif

8571 ms

05-1.gif

05-1.gif

2256 ms

logo-trans.png

logo-trans.png

19660 ms

001.gif

001.gif

19629 ms

banner1.jpg

banner1.jpg

19629 ms

banner2.jpg

banner2.jpg

19629 ms

banner3.jpg

banner3.jpg

19629 ms

mainTbg.jpg

mainTbg.jpg

12594 ms

mainBg2.gif

mainBg2.gif

13052 ms

loginbox_t1.gif

loginbox_t1.gif

13548 ms

loginbox_t2.gif

loginbox_t2.gif

15882 ms

loginbox_bg.gif

loginbox_bg.gif

16335 ms

loginbox_button.gif

loginbox_button.gif

19572 ms

loginbox_bar.gif

loginbox_bar.gif

19571 ms

T1B7m.XeXuXXaHNz_X-16-16.gif

T1B7m.XeXuXXaHNz_X-16-16.gif

279 ms

mainZX_topbg2.gif

mainZX_topbg2.gif

19990 ms

dotline.gif

dotline.gif

11884 ms

dot_vline.gif

dot_vline.gif

17994 ms

button_old_171.gif

button_old_171.gif

526 ms

button_old_51.gif

button_old_51.gif

537 ms

button_old_51.gif

button_old_51.gif

528 ms

Accessibility Review

138z.com accessibility score

43

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

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

138z.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

138z.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

    N/A

  • Encoding

    GB2312

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

138z.com

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