9.2 sec in total
1.3 sec
7.5 sec
487 ms
Click here to check amazing Rijiwang content. Otherwise, check out these important facts you probably never knew about rijiwang.com
设置路由器会遇到192.168.1.1登陆页面打不开,本站将详细介绍192.168.1.1手机登陆,falogin.cn,tplogin.cn,melogin.cn设置密码和修改密码,以及以tp-lingk路由器为例详细介绍192.168.1.1路由器设置。
Visit rijiwang.comWe analyzed Rijiwang.com page load time and found that the first response time was 1.3 sec and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
rijiwang.com performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value6.6 s
8/100
25%
Value9.5 s
11/100
10%
Value5,620 ms
0/100
30%
Value0.368
29/100
15%
Value14.0 s
10/100
10%
1260 ms
227 ms
430 ms
448 ms
46 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 21% of them (18 requests) were addressed to the original Rijiwang.com, 13% (11 requests) were made to Googleads.g.doubleclick.net and 13% (11 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Hm.baidu.com.
Page size can be reduced by 213.1 kB (42%)
503.5 kB
290.4 kB
In fact, the total size of Rijiwang.com main page is 503.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 350.0 kB which makes up the majority of the site volume.
Potential reduce by 63.7 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 63.7 kB or 85% of the original size.
Potential reduce by 4.1 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. Rijiwang images are well optimized though.
Potential reduce by 132.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 132.9 kB or 38% of the original size.
Potential reduce by 12.4 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. Rijiwang.com needs all CSS files to be minified and compressed as it can save up to 12.4 kB or 85% of the original size.
Number of requests can be reduced by 57 (75%)
76
19
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rijiwang. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.rijiwang.com
1260 ms
style.css
227 ms
jquery.fs.boxer.css
430 ms
shortcodes.css
448 ms
adsbygoogle.js
46 ms
adsbygoogle.js
130 ms
9lbx.js
276 ms
i.js
1592 ms
1469969.js
1153 ms
jquery1.7.2.min.js
907 ms
jquery.fs.boxer.min.js
550 ms
jquery.slides.min.js
551 ms
custom.js
551 ms
jquery.lazyload.min.js
903 ms
wp-embed.min.js
904 ms
wp-emoji-release.min.js
400 ms
bg.png
398 ms
logo.png
398 ms
timthumb.php
643 ms
show_ads_impl.js
202 ms
zrt_lookup.html
341 ms
cookie.js
206 ms
integrator.js
337 ms
ads
495 ms
ads
456 ms
ads
405 ms
salong.woff
262 ms
integrator.js
106 ms
ads
690 ms
reactive_library.js
30 ms
integrator.js
72 ms
ads
623 ms
85254efcadaacab5fed344cbf203b7e7.js
444 ms
load_preloaded_resource.js
566 ms
c471d9b7113df21a6cf58632ab968748.js
468 ms
abg_lite.js
491 ms
window_focus.js
454 ms
qs_click_protection.js
552 ms
rx_lidar.js
611 ms
042791247ab671b2831aa311d6583330.js
550 ms
load_preloaded_resource.js
476 ms
abg_lite.js
475 ms
window_focus.js
569 ms
qs_click_protection.js
571 ms
integrator.js
273 ms
ads
1114 ms
zrt_lookup.html
338 ms
ui
652 ms
footer_bg.png
642 ms
ads
592 ms
hm.js
2032 ms
timthumb.php
720 ms
timthumb.php
758 ms
icon.png
421 ms
s
371 ms
css2
682 ms
interstitial_ad_frame.js
342 ms
feedback_grey600_24dp.png
336 ms
settings_grey600_24dp.png
336 ms
cookie_push_onload.html
565 ms
css
464 ms
trk
683 ms
googleredir
684 ms
activeview
310 ms
gnLtmcL-mn53pq-EJRMXOCFACjpZd0iqiIv80oTeKas.js
236 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf
802 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf
810 ms
activeview
190 ms
activeview
438 ms
dpixel
760 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
963 ms
KFOmCnqEu92Fr1Me5Q.ttf
963 ms
pixel
876 ms
pixel
878 ms
activeview
591 ms
pixel
801 ms
pixel
220 ms
pixel
215 ms
pixel
215 ms
activeview
190 ms
pixel
27 ms
pixel
22 ms
hm.gif
398 ms
pixel
15 ms
pixel
14 ms
pixel
17 ms
rijiwang.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
<frame> or <iframe> elements do not have a title
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.
rijiwang.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
rijiwang.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rijiwang.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Rijiwang.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.
rijiwang.com
Open Graph description is not detected on the main page of Rijiwang. 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: