Tools & Wizards About Us
4003.com screenshot

Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

4003.com

Page Load Speed

10.9 sec in total

First Response

1.2 sec

Resources Loaded

9.5 sec

Page Rendered

210 ms

4003.com screenshot

About Website

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

400电话首选400电话网（http://www.4003.com/），400电话最大的企业400电话申请办理中心，正规渠道专业受理，确保400电话服务完善，开通快速。受理热线：400-605-6666

Visit 4003.com

Key Findings

We analyzed 4003.com page load time and found that the first response time was 1.2 sec and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster. This domain responded with an error, which can significantly jeopardize 4003.com rating and web reputation

Performance Metrics

4003.com performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

57/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.099

90/100

15%

TTI (Time to Interactive)

Value3.9 s

88/100

10%

Network Requests Diagram

4003.com

1240 ms

reset-min.css

451 ms

layout.css

921 ms

jquery-1.4.4.js

3180 ms

400.js

693 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 82% of them (46 requests) were addressed to the original 4003.com, 9% (5 requests) were made to Bdimg.share.baidu.com and 5% (3 requests) were made to 400.cn. The less responsive or slowest element that took the longest time to load (4.4 sec) relates to the external source 400.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 138.9 kB (60%)

Content Size

231.2 kB

After Optimization

92.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 4003.com main page is 231.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. Javascripts take 149.3 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 32.6 kB

  • Original 38.6 kB
  • After minification 34.6 kB
  • After compression 6.0 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 32.6 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 572 B

  • Original 31.0 kB
  • After minification 30.5 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. 4003 images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 97.7 kB

  • Original 149.3 kB
  • After minification 148.3 kB
  • After compression 51.6 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 97.7 kB or 65% of the original size.

CSS Optimization

-65%

Potential reduce by 8.0 kB

  • Original 12.3 kB
  • After minification 10.4 kB
  • After compression 4.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. 4003.com needs all CSS files to be minified and compressed as it can save up to 8.0 kB or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (35%)

Requests Now

54

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

4003.com

4003.com

1240 ms

reset-min.css

reset-min.css

451 ms

layout.css

layout.css

921 ms

jquery-1.4.4.js

jquery-1.4.4.js

3180 ms

400.js

400.js

693 ms

tj_js.asp

tj_js.asp

968 ms

kf.js

kf.js

4359 ms

top_logo.jpg

top_logo.jpg

1261 ms

body_bg.jpg

body_bg.jpg

228 ms

top_bg.jpg

top_bg.jpg

465 ms

rz.png

rz.png

239 ms

nav_go.png

nav_go.png

241 ms

nav_link_sp.gif

nav_link_sp.gif

235 ms

index_banner_bg.gif

index_banner_bg.gif

1589 ms

btn_index_4006mam.gif

btn_index_4006mam.gif

693 ms

btn_index_400mam.gif

btn_index_400mam.gif

467 ms

btn_index_phonepay.gif

btn_index_phonepay.gif

694 ms

left_top.gif

left_top.gif

686 ms

left_bg.gif

left_bg.gif

689 ms

left_title1.gif

left_title1.gif

690 ms

left_item_con1.gif

left_item_con1.gif

916 ms

left_title2.gif

left_title2.gif

917 ms

left_item_con2.gif

left_item_con2.gif

923 ms

left_tab_title_go.gif

left_tab_title_go.gif

917 ms

left_tab_title_bg.gif

left_tab_title_bg.gif

923 ms

list_prefix.gif

list_prefix.gif

1140 ms

left_title3.gif

left_title3.gif

1142 ms

left_item_con3.gif

left_item_con3.gif

1147 ms

zhifubao.gif

zhifubao.gif

1152 ms

left_bottom.gif

left_bottom.gif

1153 ms

num_info_title.gif

num_info_title.gif

1371 ms

num_info_con_bg.gif

num_info_con_bg.gif

1596 ms

num_chg_title.gif

num_chg_title.gif

1377 ms

chg_tab_go.gif

chg_tab_go.gif

1380 ms

chg_tab_title.gif

chg_tab_title.gif

1380 ms

btn_index_select.gif

btn_index_select.gif

1591 ms

hot1.gif

hot1.gif

1603 ms

liucheng.gif

liucheng.gif

1609 ms

customer_title.gif

customer_title.gif

1602 ms

client_1.gif

client_1.gif

1802 ms

client_2.gif

client_2.gif

1816 ms

client_3.gif

client_3.gif

1820 ms

client_4.gif

client_4.gif

1826 ms

AjaxGetNumber.asp

AjaxGetNumber.asp

3588 ms

h.js

h.js

694 ms

client_5.gif

client_5.gif

1630 ms

client_6.gif

client_6.gif

1812 ms

logo.gif

logo.gif

1827 ms

loading.gif

loading.gif

1828 ms

hm.gif

hm.gif

752 ms

kf.jpg

kf.jpg

3872 ms

shell_v2.js

shell_v2.js

610 ms

logger.js

logger.js

297 ms

bds_s_v2.js

bds_s_v2.js

984 ms

bdsstyle.css

bdsstyle.css

298 ms

l2.gif

l2.gif

253 ms

Accessibility Review

4003.com accessibility score

86

Accessibility Issues

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

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

Best Practices

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

4003.com SEO score

75

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 4003.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that 4003.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

4003.com

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