31.9 sec in total
2.8 sec
28.3 sec
822 ms
Welcome to fjlh.com homepage info - get ready to check Fjlh best content right away, or after learning these important things about fjlh.com
腾讯云域名注册, 腾讯云旗下品牌。腾讯云域名注册是中国领先的域名注册服务提供商, 并提供云主机、网站建设等网络服务。
Visit fjlh.comWe analyzed Fjlh.com page load time and found that the first response time was 2.8 sec and then it took 29.1 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.
fjlh.com performance score
name
value
score
weighting
Value1.8 s
90/100
10%
Value1.8 s
98/100
25%
Value6.0 s
46/100
10%
Value0 ms
100/100
30%
Value0.001
100/100
15%
Value1.9 s
100/100
10%
2843 ms
2059 ms
6714 ms
1186 ms
596 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 58% of them (42 requests) were addressed to the original Fjlh.com, 8% (6 requests) were made to Pagead2.googlesyndication.com and 8% (6 requests) were made to Bdimg.share.baidu.com. The less responsive or slowest element that took the longest time to load (14.6 sec) relates to the external source Bdimg.share.baidu.com.
Page size can be reduced by 223.1 kB (38%)
590.1 kB
367.0 kB
In fact, the total size of Fjlh.com main page is 590.1 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. 45% of websites need less resources to load. Javascripts take 270.0 kB which makes up the majority of the site volume.
Potential reduce by 29.8 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 29.8 kB or 73% of the original size.
Potential reduce by 18.7 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. Fjlh images are well optimized though.
Potential reduce by 121.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 121.5 kB or 45% of the original size.
Potential reduce by 53.2 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. Fjlh.com needs all CSS files to be minified and compressed as it can save up to 53.2 kB or 78% of the original size.
Number of requests can be reduced by 31 (46%)
68
37
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fjlh. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.
fjlh.com
2843 ms
www.fjlh.com
2059 ms
style_1_common.css
6714 ms
common.js
1186 ms
portal.js
596 ms
logging.js
598 ms
md5.js
1549 ms
adsbygoogle.js
134 ms
wxpublic.css
1554 ms
ping.js
1694 ms
discuz_tips.js
585 ms
background.png
282 ms
logo.png
1677 ms
wx_jqr.gif
285 ms
75ce99cc73184048ad670d341272f339.jpg
6972 ms
d02d8e5f8227d92d764be283db5df926.jpg
6431 ms
39b02f9b3602b94fac584b190b168498.jpg
831 ms
eb284f4ea265dcf286c271e3e48af2f6.jpg
1789 ms
b1d88dd06ff69000d8b035fdc7ef00a3.jpg
1415 ms
380d2ffe3533013edac9d22c29fc2333.jpg
1673 ms
qrcode_fjlh150200.gif
1786 ms
ad_close.gif
1940 ms
wxbt.png
1947 ms
wxlogo.jpg
2255 ms
wx.png
2044 ms
security.png
2237 ms
px.png
2232 ms
newarow.gif
2300 ms
pn.png
2553 ms
nv.png
2553 ms
qmenu.png
2583 ms
nv_a.png
3439 ms
mu_bg.png
2844 ms
search.png
2869 ms
ca-pub-3953272315700288.js
383 ms
zrt_lookup.html
374 ms
show_ads_impl.js
226 ms
common_extra.js
3452 ms
bs_7_ft.png
3069 ms
bs_7_hd.png
3956 ms
bs_7_ft_r.png
3373 ms
dot.gif
3716 ms
bs_6_ft.png
3723 ms
bs_6_hd.png
3732 ms
bs_6_ft_r.png
4031 ms
thead.png
4049 ms
title.png
4047 ms
Mjc3NzA4MTI=.js
397 ms
share.js
744 ms
h.js
1713 ms
ads
355 ms
osd.js
78 ms
ads
337 ms
css
299 ms
m_js_controller.js
314 ms
abg.js
447 ms
favicon
299 ms
googlelogo_color_112x36dp.png
321 ms
mobile_unified_button_icon_white.png
88 ms
imgad
156 ms
x_button_blue2.png
172 ms
PuwvqkdbcqU-fCZ9Ed-b7S3USBnSvpkopQaUR-2r7iU.ttf
419 ms
s
150 ms
Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js
60 ms
hm.gif
363 ms
scrolltop.png
2398 ms
slide_api.js
371 ms
slide_view.js
14615 ms
tangram.js
2332 ms
api_base.js
567 ms
activeview
64 ms
logger.js
1363 ms
fjlh.com accessibility score
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
fjlh.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
General
Impact
Issue
Detected JavaScript libraries
fjlh.com SEO score
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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fjlh.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 Fjlh.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.
fjlh.com
Open Graph description is not detected on the main page of Fjlh. 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: