47.6 sec in total
11.2 sec
36.2 sec
180 ms
Welcome to ywhy411.com homepage info - get ready to check Ywhy 411 best content right away, or after learning these important things about ywhy411.com
Visit ywhy411.comWe analyzed Ywhy411.com page load time and found that the first response time was 11.2 sec and then it took 36.4 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 30 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
ywhy411.com performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value8.3 s
2/100
25%
Value4.3 s
76/100
10%
Value90 ms
99/100
30%
Value0.014
100/100
15%
Value4.0 s
88/100
10%
11212 ms
2060 ms
9879 ms
313 ms
1659 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 84% of them (48 requests) were addressed to the original Ywhy411.com, 14% (8 requests) were made to Tp.shabc.net and 2% (1 request) were made to Pv.sohu.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Tp.shabc.net.
Page size can be reduced by 166.1 kB (55%)
300.4 kB
134.3 kB
In fact, the total size of Ywhy411.com main page is 300.4 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. 20% of websites need less resources to load. Javascripts take 169.8 kB which makes up the majority of the site volume.
Potential reduce by 480 B
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 480 B or 66% of the original size.
Potential reduce by 9.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. Obviously, Ywhy 411 needs image optimization as it can save up to 9.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 118.0 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 118.0 kB or 69% of the original size.
Potential reduce by 38.7 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. Ywhy411.com needs all CSS files to be minified and compressed as it can save up to 38.7 kB or 85% of the original size.
Number of requests can be reduced by 11 (44%)
25
14
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ywhy 411. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
ywhy411.com
11212 ms
main.css
2060 ms
nav.js
9879 ms
MSClass.js
313 ms
aqijs.js
1659 ms
503.js
318 ms
1418265911.js
1111 ms
webchange.js
13 ms
jquery.js
2245 ms
common.js
921 ms
index.js
921 ms
411_change.js
15 ms
rlswt.js
19997 ms
tongji.js
1430 ms
swt_change.js
9 ms
cityjson
954 ms
503.html
3858 ms
yiyuan.jpg
19749 ms
youc2.jpg
3065 ms
zt1.jpg
19748 ms
rl_img1.jpg
15797 ms
xing_5.png
3373 ms
233.png
7677 ms
rlcs_1.jpg
11621 ms
rlcs_5.jpg
8302 ms
rlcs_2.jpg
19746 ms
rlcs_3.jpg
19746 ms
rlcs_6.jpg
15043 ms
yyimg.jpg
19746 ms
yyimg1.jpg
19686 ms
yyimg2.jpg
19746 ms
yyimg3.jpg
19745 ms
yyimg4.jpg
19744 ms
ry1.jpg
19744 ms
ry2.jpg
19744 ms
ry5.jpg
19743 ms
ry4.jpg
19743 ms
ry6.jpg
19743 ms
ry3.jpg
19742 ms
hj1.jpg
19743 ms
hj2.jpg
19742 ms
hj3.jpg
19742 ms
hj4.jpg
19743 ms
hj5.jpg
19742 ms
hj6.jpg
19742 ms
gy1.jpg
19741 ms
gy2.jpg
19743 ms
gy3.jpg
19744 ms
gy4.jpg
19745 ms
gy5.jpg
19745 ms
gy6.jpg
19743 ms
jigimg.jpg
19741 ms
lc_1.png
19740 ms
lc_2.png
19682 ms
lc_3.png
17363 ms
lc_4.png
13057 ms
lc_5.png
12433 ms
ywhy411.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
Image elements do not have [alt] attributes
Links do not have a discernible 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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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
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.
ywhy411.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
General
Impact
Issue
Detected JavaScript libraries
ywhy411.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
ZH
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ywhy411.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 Ywhy411.com main page’s claimed encoding is . 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.
ywhy411.com
Open Graph description is not detected on the main page of Ywhy 411. 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: