7.3 sec in total
1.2 sec
5.9 sec
242 ms
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.comWe analyzed Ft22.com page load time and found that the first response time was 1.2 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
ft22.com performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value2.9 s
80/100
25%
Value8.6 s
17/100
10%
Value70 ms
99/100
30%
Value0.608
10/100
15%
Value5.9 s
65/100
10%
1164 ms
674 ms
906 ms
1383 ms
688 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 88% of them (49 requests) were addressed to the original Ft22.com, 9% (5 requests) were made to Bdimg.share.baidu.com and 4% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Ft22.com.
Page size can be reduced by 134.4 kB (13%)
998.3 kB
863.8 kB
In fact, the total size of Ft22.com main page is 998.3 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 842.5 kB which makes up the majority of the site volume.
Potential reduce by 39.5 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 39.5 kB or 78% of the original size.
Potential reduce by 66.0 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.
Potential reduce by 20.9 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 20.9 kB or 25% of the original size.
Potential reduce by 8.0 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 8.0 kB or 37% of the original size.
Number of requests can be reduced by 19 (35%)
55
36
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 14 to 1 for JavaScripts and as a result speed up the page load time.
ft22.com
1164 ms
bw-loader-413.5.8.js
674 ms
css.css
906 ms
jquery.min.js
1383 ms
jquery.marqueeUI.js
688 ms
jquery.rotaion.js
460 ms
jquery.slide.js
680 ms
scroll.js
689 ms
scroll3.js
984 ms
jquery.duilian.js
984 ms
jquery.textUI.js
991 ms
jquery.chinacourtUI.js
996 ms
user.asp
1298 ms
autopublisher.asp
1066 ms
header_bg.png
227 ms
top_bg.png
226 ms
1256599093.jpg
458 ms
162744753.jpg
917 ms
225366545.jpg
458 ms
92599033.jpg
519 ms
127111033.jpg
3466 ms
1132333241.jpg
1122 ms
949233173.jpg
687 ms
187344205.jpg
688 ms
1429577861.jpg
743 ms
2014040447570845.gif
1374 ms
2014040447215297.gif
2603 ms
158477253.jpg
967 ms
1112377081.jpg
1144 ms
1935488753.jpg
1191 ms
1051544781.jpg
1346 ms
758333125.jpg
1374 ms
92211393.jpg
1415 ms
websites.jpg
1570 ms
gabeian.png
2836 ms
lg_em_bg.png
1580 ms
logo_bg.png
3728 ms
nav_bg.png
1773 ms
nav_bg1.png
1809 ms
home_bg.png
1999 ms
tuijian.png
2039 ms
li_bg.png
2222 ms
button_gk.png
2206 ms
lf_btn1.png
2386 ms
rt_btn1.png
2435 ms
role.png
2610 ms
ft22_indexlyb.png
2664 ms
scrollicon.png
2745 ms
grad_bg.png
2835 ms
hm.js
946 ms
shell_v2.js
866 ms
logger.js
241 ms
bds_s_v2.js
424 ms
hm.gif
284 ms
bdsstyle.css
216 ms
r7.gif
298 ms
ft22.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<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
Image elements do not have [alt] attributes
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
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
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
ft22.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
ft22.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
ZH
EN
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 it does not match the claimed English language. 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.
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: