Tools & Wizards About Us
110.com screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 38

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

110.com

法律咨询|律师在线 - 110网在线律师免费解答在线法律咨询

Page Load Speed

6.6 sec in total

First Response

727 ms

Resources Loaded

5.7 sec

Page Rendered

240 ms

110.com screenshot

About Website

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

110法律咨询网提供免费法律咨询、律师在线咨询、法律法规查询、点对点法律咨询解答、在线案件委托。劳动合同律师、婚姻法律师、刑事辩护律师等为您提供在线律师咨询服务

Visit 110.com

Key Findings

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

Performance Metrics

110.com performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

40/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.1 s

87/100

10%

Network Requests Diagram

110.com

727 ms

www.110.com

937 ms

index.css

495 ms

index.js

493 ms

message.js

497 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original 110.com, 77% (57 requests) were made to Img.110.com and 11% (8 requests) were made to Img1.110.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Img.110.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 115.1 kB (23%)

Content Size

491.8 kB

After Optimization

376.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 93.3 kB

  • Original 112.6 kB
  • After minification 112.5 kB
  • After compression 19.3 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 93.3 kB or 83% of the original size.

Image Optimization

-5%

Potential reduce by 16.9 kB

  • Original 357.3 kB
  • After minification 340.4 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. 110 images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 3.1 kB

  • Original 15.0 kB
  • After minification 14.7 kB
  • After compression 11.8 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 3.1 kB or 21% of the original size.

CSS Optimization

-25%

Potential reduce by 1.7 kB

  • Original 6.9 kB
  • After minification 6.9 kB
  • After compression 5.1 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. 110.com needs all CSS files to be minified and compressed as it can save up to 1.7 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (31%)

Requests Now

72

After Optimization

50

  • Images
  • JavaScript
  • CSS

The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 110. 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 as a result speed up the page load time.

Network Requests Diagram

110.com

110.com

727 ms

www.110.com

www.110.com

937 ms

index.css

index.css

495 ms

index.js

index.js

493 ms

message.js

message.js

497 ms

sheng.php

sheng.php

458 ms

region1.js

region1.js

517 ms

shindex.js

shindex.js

645 ms

addhf.js

addhf.js

442 ms

appad.js

appad.js

495 ms

tj.js

tj.js

604 ms

10523113241.jpg

10523113241.jpg

889 ms

dls.jpg

dls.jpg

617 ms

xxxtop.gif

xxxtop.gif

407 ms

xxxbg.gif

xxxbg.gif

408 ms

xxxsunvbg.gif

xxxsunvbg.gif

409 ms

xxxlogobg.gif

xxxlogobg.gif

409 ms

11001.gif

11001.gif

425 ms

kefu.gif

kefu.gif

589 ms

ad329x90b.jpg

ad329x90b.jpg

819 ms

ad329x90d.jpg

ad329x90d.jpg

818 ms

ad329x90a.jpg

ad329x90a.jpg

818 ms

ad329x90c.jpg

ad329x90c.jpg

1026 ms

xxxlawyer.gif

xxxlawyer.gif

833 ms

4778566.jpg

4778566.jpg

997 ms

user_online.gif

user_online.gif

1224 ms

8359173.jpg

8359173.jpg

1224 ms

47174.jpg

47174.jpg

1227 ms

14731.jpg

14731.jpg

1246 ms

1189878.jpg

1189878.jpg

1405 ms

853474.jpg

853474.jpg

1439 ms

1116386.jpg

1116386.jpg

1638 ms

18068937.jpg

18068937.jpg

1632 ms

21635570.jpg

21635570.jpg

1633 ms

14890525.jpg

14890525.jpg

1658 ms

477990.jpg

477990.jpg

1814 ms

117060.jpg

117060.jpg

1845 ms

3407230.jpg

3407230.jpg

2043 ms

4850486.jpg

4850486.jpg

2044 ms

21636411.jpg

21636411.jpg

2044 ms

rr01.gif

rr01.gif

2063 ms

ll01.gif

ll01.gif

2223 ms

111663.jpg

111663.jpg

2253 ms

HY.jpg

HY.jpg

2454 ms

LD.jpg

LD.jpg

2454 ms

jt.jpg

jt.jpg

2472 ms

flww.jpg

flww.jpg

410 ms

lszxzx.jpg

lszxzx.jpg

1037 ms

lsft1.jpg

lsft1.jpg

413 ms

adr.jpg

adr.jpg

457 ms

flww.jpg

flww.jpg

745 ms

10503916491.jpg

10503916491.jpg

971 ms

ht.jpg

ht.jpg

2494 ms

xs.jpg

xs.jpg

2607 ms

tz.jpg

tz.jpg

419 ms

YL.jpg

YL.jpg

2442 ms

hm.js

hm.js

964 ms

searchbg.gif

searchbg.gif

2455 ms

menu.gif

menu.gif

2454 ms

menu_hover.gif

menu_hover.gif

2478 ms

xxxshowpath.gif

xxxshowpath.gif

2508 ms

showpage.gif

showpage.gif

2610 ms

nav.png

nav.png

2481 ms

mleftbg.gif

mleftbg.gif

2456 ms

arrow.gif

arrow.gif

2457 ms

xxxlawyera.gif

xxxlawyera.gif

2471 ms

lawbg.gif

lawbg.gif

2492 ms

lawerbanshi_04.gif

lawerbanshi_04.gif

2449 ms

xxxtit.gif

xxxtit.gif

2452 ms

hot.gif

hot.gif

2478 ms

a_num.gif

a_num.gif

2506 ms

a_num01.gif

a_num01.gif

2504 ms

ztls.gif

ztls.gif

2487 ms

hm.gif

hm.gif

291 ms

Accessibility Review

110.com accessibility score

38

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

Form elements do not have associated labels

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

110.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

110.com SEO score

77

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

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

110.com

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