Tools & Wizards About Us
35.com screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

35.com

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

Page Load Speed

18 sec in total

First Response

577 ms

Resources Loaded

17.2 sec

Page Rendered

278 ms

35.com screenshot

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 577 ms and then it took 17.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

35.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.712

7/100

15%

TTI (Time to Interactive)

Value3.8 s

90/100

10%

Network Requests Diagram

35.com

577 ms

1093 ms

base.css

504 ms

skin.css

798 ms

35com.css

1066 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 95% of them (80 requests) were addressed to the original 35.com, 2% (2 requests) were made to Hm.baidu.com and 1% (1 request) were made to Kxlogo.knet.cn. The less responsive or slowest element that took the longest time to load (13.7 sec) belongs to the original domain 35.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 561.6 kB (18%)

Content Size

3.0 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 35.com main page is 3.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 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 56.3 kB

  • Original 69.2 kB
  • After minification 56.6 kB
  • After compression 12.9 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 12.6 kB, which is 18% 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 56.3 kB or 81% of the original size.

Image Optimization

-8%

Potential reduce by 208.2 kB

  • Original 2.6 MB
  • After minification 2.4 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. 35 images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 196.7 kB

  • Original 267.2 kB
  • After minification 222.2 kB
  • After compression 70.5 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 196.7 kB or 74% of the original size.

CSS Optimization

-81%

Potential reduce by 100.5 kB

  • Original 124.1 kB
  • After minification 106.5 kB
  • After compression 23.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 100.5 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

81

After Optimization

65

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

35.com

35.com

577 ms

1093 ms

base.css

base.css

504 ms

skin.css

skin.css

798 ms

35com.css

35com.css

1066 ms

jqueryv16.js

jqueryv16.js

1327 ms

com.js

com.js

522 ms

tabControl.js

tabControl.js

790 ms

flexslider.css

flexslider.css

548 ms

jquery.flexslider.js

jquery.flexslider.js

1131 ms

donews_new35.js

donews_new35.js

801 ms

ticker-style.css

ticker-style.css

799 ms

jquery.ticker.js

jquery.ticker.js

813 ms

seallogo.dll

seallogo.dll

794 ms

NewBase.js

NewBase.js

1105 ms

logo.png

logo.png

505 ms

header-text.png

header-text.png

262 ms

atte.jpg

atte.jpg

258 ms

listen.jpg

listen.jpg

259 ms

nav-bg.png

nav-bg.png

263 ms

nav-in-bg.png

nav-in-bg.png

497 ms

nav-a-bg.png

nav-a-bg.png

524 ms

submenu-right-bg.png

submenu-right-bg.png

527 ms

li-35cloud.png

li-35cloud.png

525 ms

cloud-apply.gif

cloud-apply.gif

784 ms

siteNav.png

siteNav.png

747 ms

sitenav-top-bg.png

sitenav-top-bg.png

761 ms

wechatbinding.png

wechatbinding.png

2379 ms

banner_top160406.jpg

banner_top160406.jpg

1619 ms

huojian.jpg

huojian.jpg

2901 ms

banner_frist.jpg

banner_frist.jpg

6134 ms

get_prize_banner.jpg

get_prize_banner.jpg

2621 ms

mailchat.png

mailchat.png

13337 ms

lvzhengyou1.png

lvzhengyou1.png

13736 ms

miniOA.jpg

miniOA.jpg

10336 ms

35cloud_new.jpg

35cloud_new.jpg

6317 ms

35cloudoffice-banner_new.jpg

35cloudoffice-banner_new.jpg

9597 ms

35comcode-img.jpg

35comcode-img.jpg

7854 ms

could-dw_01.png

could-dw_01.png

7084 ms

could-dw_03.png

could-dw_03.png

10744 ms

comNav1.png

comNav1.png

8104 ms

comNav2.png

comNav2.png

8385 ms

comNav3.png

comNav3.png

8654 ms

comNav4.png

comNav4.png

8905 ms

comNav5.png

comNav5.png

9158 ms

fangpian.png

fangpian.png

11660 ms

safety1.png

safety1.png

9855 ms

safety2.png

safety2.png

10118 ms

ei_normal.png

ei_normal.png

10396 ms

icann.jpg

icann.jpg

10575 ms

cnnic_en.png

cnnic_en.png

1817 ms

hm.js

hm.js

742 ms

35ewave.apk.png

35ewave.apk.png

10431 ms

ewave-ios.apk.jpg

ewave-ios.apk.jpg

12186 ms

35pushmail.apk.png

35pushmail.apk.png

11249 ms

pushmail-ios.apk.jpg

pushmail-ios.apk.jpg

11263 ms

35pushoa.apk.png

35pushoa.apk.png

11505 ms

pushoa-ios.apk.jpg

pushoa-ios.apk.jpg

12044 ms

banner_bg.png

banner_bg.png

11661 ms

bg1.png

bg1.png

11500 ms

35comcode.jpg

35comcode.jpg

11754 ms

could-dw.png

could-dw.png

12892 ms

app-down.gif

app-down.gif

11798 ms

iproitemleftbg.png

iproitemleftbg.png

11938 ms

iPro3.png

iPro3.png

12013 ms

hm.gif

hm.gif

357 ms

flexslider-icon.woff

flexslider-icon.woff

11186 ms

ico1.png

ico1.png

10576 ms

iPro2.png

iPro2.png

10448 ms

iPro1.png

iPro1.png

10171 ms

bg2.png

bg2.png

7078 ms

submitQA1.png

submitQA1.png

7006 ms

submitQA2.png

submitQA2.png

6244 ms

comBranch.png

comBranch.png

5615 ms

newspage.png

newspage.png

5471 ms

line1.png

line1.png

5198 ms

ico3.png

ico3.png

4941 ms

35bc-c.png

35bc-c.png

4761 ms

35ass-c.png

35ass-c.png

4575 ms

icon.png

icon.png

5042 ms

ewave.jpg

ewave.jpg

4016 ms

youqia.png

youqia.png

3761 ms

oa.jpg

oa.jpg

3585 ms

banner_img_download.png

banner_img_download.png

3588 ms

Accessibility Review

35.com accessibility score

61

Accessibility Issues

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

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

Low

Detected JavaScript libraries

SEO Factors

35.com SEO score

80

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

    GBK

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 neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 35.com main page’s claimed encoding is gbk. 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

35.com

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: