Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

35.com

域名注册_企业邮箱_云主机_ssl安全证书_网络推广 | 三五云商城

Page Load Speed

5.1 sec in total

First Response

750 ms

Resources Loaded

4.3 sec

Page Rendered

62 ms

About Website

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

三五云商城是三五互联旗下产品的线上商城,主要提供域名、企业邮箱、办公软件、虚拟主机、网站建设等服务。

Visit 35.com

Key Findings

We analyzed 35.com page load time and found that the first response time was 750 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

35.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.8 s

0/100

25%

SI (Speed Index)

Value23.8 s

0/100

10%

TBT (Total Blocking Time)

Value1,950 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.094

91/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

35.com

750 ms

index.html

400 ms

index-cf554051.css

865 ms

hm.js

1201 ms

Our browser made a total of 4 requests to load all elements on the main page. We found that 75% of them (3 requests) were addressed to the original 35.com, 25% (1 request) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Hm.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 39.3 kB (32%)

Content Size

121.2 kB

After Optimization

81.9 kB

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

HTML Optimization

-80%

Potential reduce by 8.6 kB

  • Original 10.7 kB
  • After minification 9.4 kB
  • After compression 2.2 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 1.3 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 8.6 kB or 80% of the original size.

CSS Optimization

-28%

Potential reduce by 30.7 kB

  • Original 110.4 kB
  • After minification 110.4 kB
  • After compression 79.7 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. 35.com needs all CSS files to be minified and compressed as it can save up to 30.7 kB or 28% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 35. According to our analytics all requests are already optimized.

Accessibility Review

35.com accessibility score

84

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.

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

35.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

High

Missing source maps for large first-party JavaScript

SEO Factors

35.com SEO score

74

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

High

robots.txt is not valid

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

    EN

  • Encoding

    UTF-8

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