5.4 sec in total
698 ms
4.3 sec
367 ms
Welcome to web191.com homepage info - get ready to check Web 191 best content right away, or after learning these important things about web191.com
网站建设,网站制作,企业网站建设,企业网站开发,郑州,商务网站建设,商务网站制作
Visit web191.comWe analyzed Web191.com page load time and found that the first response time was 698 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
web191.com performance score
name
value
score
weighting
Value2.6 s
62/100
10%
Value19.3 s
0/100
25%
Value12.9 s
2/100
10%
Value1,140 ms
22/100
30%
Value0.309
38/100
15%
Value21.9 s
1/100
10%
698 ms
933 ms
455 ms
947 ms
689 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 45% of them (43 requests) were addressed to the original Web191.com, 54% (52 requests) were made to Udify.app and 1% (1 request) were made to Static.cloudflareinsights.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Web191.com.
Page size can be reduced by 273.6 kB (17%)
1.6 MB
1.4 MB
In fact, the total size of Web191.com main page is 1.6 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 15.4 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 15.4 kB or 73% of the original size.
Potential reduce by 232.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, Web 191 needs image optimization as it can save up to 232.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 20.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 20.5 kB or 21% of the original size.
Potential reduce by 5.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. Web191.com needs all CSS files to be minified and compressed as it can save up to 5.0 kB or 40% of the original size.
Number of requests can be reduced by 59 (62%)
95
36
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Web 191. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
web191.com
698 ms
style.css
933 ms
lrtk.css
455 ms
jquery-1.8.0.min.js
947 ms
mosaic.1.0.1.js
689 ms
lrtk.js
929 ms
jquery-1.7.1.min.js
1395 ms
js.js
1151 ms
jquery.kinmaxshow-1.1.min.js
1171 ms
jquery.superslide.2.1.1.js
1379 ms
embed.min.js
108 ms
oc6ax5R47O3v7RVS
88 ms
logo.png
906 ms
1.jpg
1076 ms
sub_1_1.png
901 ms
2.jpg
1648 ms
sub_2_2.png
1323 ms
3.jpg
667 ms
sub_3_2.png
1592 ms
btbg.png
1772 ms
fl_up.jpg
1134 ms
fuwu1.png
1281 ms
fuwu2.png
1363 ms
fuwu3.png
1524 ms
fuwu4.png
1558 ms
fenge.png
1601 ms
iabotu.jpg
1927 ms
bg-black.png
1802 ms
1-1511262350440-L.jpg
2331 ms
1-1511262350260-L.png
1829 ms
1-1511262349200-L.jpg
1869 ms
1-151126234U80-L.jpg
1994 ms
1-151126234R00-L.jpg
2034 ms
1-151126234J60-L.jpg
2067 ms
1-151126234G10-L.jpg
2110 ms
1-1511262345100-L.png
2645 ms
weixin.png
2199 ms
b58db3eb4b0ca749.css
18 ms
dbbfeb6ba09a7496.css
44 ms
e5d9714c3a739ed3.css
119 ms
fd9d1056-3d0b44fc34e7e5d4.js
51 ms
8069-3c33bdf50ac3eeb0.js
249 ms
main-app-ba57c34681fa8494.js
41 ms
15372279-02f7a0afb3c4217c.js
36 ms
c0e397d0-c5b9fa1215192c37.js
59 ms
d3ac728e-0bbe95305fb72ce4.js
64 ms
ad2d9488-3ebd8b4b6af0c977.js
61 ms
379-4385abf7afc183ea.js
81 ms
8682-e98d0f15ce955448.js
69 ms
5146-a06dd7fc04c8c221.js
88 ms
441-f6bebd3f4a91f9f5.js
98 ms
5250-ee61bbacaebccc1b.js
92 ms
2133-1b87e4681176dc59.js
96 ms
2561-d085ef2f6c53cd04.js
108 ms
1143-09f9101985ce3789.js
118 ms
1611-53c56c86ff29ca06.js
119 ms
695-425ec325af2ee87b.js
118 ms
4609-302c208f146b9291.js
126 ms
3802-e25d4d8fb7be6d47.js
137 ms
828-fee024c6d476ebce.js
135 ms
3566-285854ac82c0ca0a.js
161 ms
9270-cef9993fd5d1dc64.js
148 ms
8620-b5bd25fcb6f56c24.js
145 ms
7592-956bfbb683345461.js
166 ms
5841-2d86fde13fe728e4.js
157 ms
1242-dd6d2a8f13a047d6.js
171 ms
730-d8005350da9c0b7a.js
170 ms
1582-7db712d392dc8e95.js
191 ms
716-69566c18ff62cdaf.js
199 ms
755-10cfc259bd592d12.js
195 ms
7953-ccde9d5ffefde56b.js
191 ms
7635-bda553f997db4803.js
198 ms
vef91dfe02fce4ee0ad053f6de4f175db1715022073587
97 ms
7243-c3450f42c88f67d9.js
243 ms
1489-3e923b41436b18ed.js
191 ms
6709-e40b5e6105807a11.js
179 ms
page-0f75168cade22f5f.js
182 ms
3374-d92d30aa2eaed621.js
183 ms
5935-d40f132cb46f5aac.js
188 ms
2029-d88e97ad2875cc56.js
174 ms
3636-e03cb650206b4f91.js
191 ms
9483-0fe3981bf5c853ee.js
184 ms
layout-718b59526a035d3b.js
178 ms
396464d2-6a0f8b06ca451b7e.js
183 ms
9933-ef7caa854bf257d4.js
176 ms
layout-7bc79828c54befaa.js
173 ms
polyfills-c67a75d1b6f99dc8.js
184 ms
webpack-d9f18b1e4eda457b.js
178 ms
bsbg.png
1816 ms
icons.png
816 ms
r_qq.png
856 ms
qqbg.png
928 ms
r_wx.png
999 ms
r_phone.png
1042 ms
r_top.png
1077 ms
button.png
1037 ms
web191.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.
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
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
web191.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
Missing source maps for large first-party JavaScript
web191.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Web191.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 Web191.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.
web191.com
Open Graph description is not detected on the main page of Web 191. 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: