Tools & Wizards About Us
ft22.com screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    80% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

ft22.com

工伤法律门户_发生工伤必上的法律网站

Page Load Speed

41.7 sec in total

First Response

2.3 sec

Resources Loaded

39.1 sec

Page Rendered

253 ms

ft22.com screenshot

About Website

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

专业的工伤法律服务网站，提供工伤保险条例及各省工伤保险实施办法查询，计算工伤赔偿标准，解答工伤法律咨询，由工伤律师代理疑难工伤案例。

Visit ft22.com

Key Findings

We analyzed Ft22.com page load time and found that the first response time was 2.3 sec and then it took 39.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

ft22.com performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

77/100

25%

SI (Speed Index)

Value8.0 s

21/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.607

10/100

15%

TTI (Time to Interactive)

Value5.4 s

72/100

10%

Network Requests Diagram

ft22.com

2305 ms

www.ft22.com

7863 ms

ccc.css

4457 ms

wb.js

6 ms

o.php

2204 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 45% of them (26 requests) were addressed to the original Ft22.com, 9% (5 requests) were made to Bdimg.share.baidu.com and 7% (4 requests) were made to Tjs.sjs.sinajs.cn. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Bdimg.share.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 334.7 kB (57%)

Content Size

591.6 kB

After Optimization

256.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-91%

Potential reduce by 176.0 kB

  • Original 194.0 kB
  • After minification 186.2 kB
  • After compression 18.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 176.0 kB or 91% of the original size.

Image Optimization

-4%

Potential reduce by 2.4 kB

  • Original 57.2 kB
  • After minification 54.8 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. Ft 22 images are well optimized though.

JavaScript Optimization

-42%

Potential reduce by 128.4 kB

  • Original 303.9 kB
  • After minification 280.3 kB
  • After compression 175.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 128.4 kB or 42% of the original size.

CSS Optimization

-77%

Potential reduce by 27.9 kB

  • Original 36.5 kB
  • After minification 31.6 kB
  • After compression 8.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. Ft22.com needs all CSS files to be minified and compressed as it can save up to 27.9 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (49%)

Requests Now

55

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ft22.com

ft22.com

2305 ms

www.ft22.com

www.ft22.com

7863 ms

ccc.css

ccc.css

4457 ms

wb.js

wb.js

6 ms

o.php

o.php

2204 ms

user.asp

user.asp

893 ms

adsbygoogle.js

adsbygoogle.js

9 ms

autopublisher.asp

autopublisher.asp

509 ms

qrcode.js

qrcode.js

2007 ms

logo.jpg

logo.jpg

968 ms

zsq.jpg

zsq.jpg

2496 ms

me22.gif

me22.gif

929 ms

me11.gif

me11.gif

1382 ms

t11.gif

t11.gif

4126 ms

t22.gif

t22.gif

5241 ms

me44.gif

me44.gif

2344 ms

me33.gif

me33.gif

5655 ms

t33.gif

t33.gif

2311 ms

t44.gif

t44.gif

4506 ms

zhang.jpg

zhang.jpg

2827 ms

2013071537016985.jpg

2013071537016985.jpg

6196 ms

2013042759937581.jpg

2013042759937581.jpg

3779 ms

2013032270967017.jpg

2013032270967017.jpg

4242 ms

2013031668814473.jpg

2013031668814473.jpg

5496 ms

btn_s2.gif

btn_s2.gif

4700 ms

nZxzx.gif

nZxzx.gif

4952 ms

cdh.jpg

cdh.jpg

5149 ms

ca-pub-8412424304988664.js

ca-pub-8412424304988664.js

129 ms

zrt_lookup.html

zrt_lookup.html

71 ms

show_ads_impl.js

show_ads_impl.js

70 ms

xxian.jpg

xxian.jpg

6411 ms

top-dhbj2.jpg

top-dhbj2.jpg

5539 ms

cdh1.jpg

cdh1.jpg

5562 ms

h.js

h.js

2754 ms

ads

ads

136 ms

osd.js

osd.js

12 ms

s.js

s.js

3884 ms

hm.gif

hm.gif

1154 ms

shell_v2.js

shell_v2.js

3253 ms

ga.js

ga.js

36 ms

loading1.gif

loading1.gif

30 ms

bundle.js

bundle.js

30 ms

client.js

client.js

40 ms

__utm.gif

__utm.gif

61 ms

iframeWidget.js

iframeWidget.js

65 ms

aj_relationship.php

aj_relationship.php

891 ms

followbutton.php

followbutton.php

1769 ms

followButton.css

followButton.css

9 ms

sso.js

sso.js

5 ms

followButton.js

followButton.js

5 ms

suda.js

suda.js

5 ms

b.gif

b.gif

700 ms

bg_flbtn.png

bg_flbtn.png

2 ms

icon_user.png

icon_user.png

3 ms

logger.js

logger.js

19617 ms

bds_s_v2.js

bds_s_v2.js

14579 ms

bdsstyle.css

bdsstyle.css

279 ms

r7.gif

r7.gif

550 ms

Accessibility Review

ft22.com accessibility score

52

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

ft22.com best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

ft22.com SEO score

89

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

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

    GB2312

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

ft22.com

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