48.8 sec in total
4.6 sec
43.7 sec
527 ms
Welcome to underriver.net homepage info - get ready to check Underriver best content right away, or after learning these important things about underriver.net
这只是一个无聊的博客。
Visit underriver.netWe analyzed Underriver.net page load time and found that the first response time was 4.6 sec and then it took 44.2 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 were 9 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
underriver.net performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value3.2 s
71/100
25%
Value9.2 s
13/100
10%
Value670 ms
44/100
30%
Value0
100/100
15%
Value12.9 s
13/100
10%
4551 ms
3495 ms
928 ms
3403 ms
1083 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 61% of them (22 requests) were addressed to the original Underriver.net, 19% (7 requests) were made to Secure.gravatar.com and 3% (1 request) were made to Static.fatesinger.com. The less responsive or slowest element that took the longest time to load (20 sec) belongs to the original domain Underriver.net.
Page size can be reduced by 119.8 kB (55%)
216.3 kB
96.6 kB
In fact, the total size of Underriver.net main page is 216.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. Only 10% of websites need less resources to load. Javascripts take 72.8 kB which makes up the majority of the site volume.
Potential reduce by 24.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 24.0 kB or 77% of the original size.
Potential reduce by 10.6 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. Obviously, Underriver needs image optimization as it can save up to 10.6 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 52.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 52.5 kB or 72% of the original size.
Potential reduce by 32.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. Underriver.net needs all CSS files to be minified and compressed as it can save up to 32.6 kB or 78% of the original size.
Number of requests can be reduced by 7 (29%)
24
17
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Underriver. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
underriver.net
4551 ms
wp-emoji-release.min.js
3495 ms
style.css
928 ms
app.css
3403 ms
style.css
1083 ms
jquery.js
19690 ms
jquery-migrate.min.js
16882 ms
index.js
1376 ms
index.js
3287 ms
app.js
1278 ms
wp-embed.min.js
1718 ms
0o32egv38z1b8rkb.png!pussy
2676 ms
9de7e1aeed66eaaee2c98a815062c481
458 ms
logo-u.png
5204 ms
icons.svg
7686 ms
fools-day.jpg
17468 ms
img_0459-1.jpg
19979 ms
happynewyear-1024x497.jpg
19978 ms
ssl.jpg
19979 ms
rds-2.jpg
19978 ms
goodbye2015-1024x640.jpg
19979 ms
IMG_7373-1024x683.jpg
19978 ms
IMG_0258-0.jpg
19979 ms
flarum.jpg
19978 ms
11d699a3010872e1c1abc8fe35d3938e
377 ms
8b7b2d5a405902f483a6ae1ad6d96718
400 ms
4c70398463788150f06e22bd90938a3b
356 ms
6f46708904855dd89ff658b0328b8f88
363 ms
39647308cc73ce966ec06cb3453da6dc
284 ms
b18a4afaf282d26b69267c8502e5f0af
364 ms
stat.php
2472 ms
stat.htm
223 ms
core.php
890 ms
9.gif
837 ms
pic1.gif
1289 ms
app.gif
1044 ms
underriver.net 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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
underriver.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
underriver.net 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
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Underriver.net 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 Underriver.net 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.
underriver.net
Open Graph description is not detected on the main page of Underriver. 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: