11.7 sec in total
651 ms
10.7 sec
393 ms
Visit a187.com now to see the best up-to-date A 187 content and also check out these interesting facts you probably never knew about a187.com
999宝藏网-06-19年记录-历史百度权重4
Visit a187.comWe analyzed A187.com page load time and found that the first response time was 651 ms and then it took 11.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
a187.com performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value3.0 s
77/100
25%
Value5.6 s
53/100
10%
Value60 ms
100/100
30%
Value0.447
20/100
15%
Value3.0 s
96/100
10%
651 ms
832 ms
221 ms
418 ms
617 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original A187.com, 80% (56 requests) were made to Bbs.999gho.com and 7% (5 requests) were made to Bdimg.share.baidu.com. The less responsive or slowest element that took the longest time to load (4.7 sec) relates to the external source Icon.cnzz.com.
Page size can be reduced by 248.9 kB (30%)
819.1 kB
570.1 kB
In fact, the total size of A187.com main page is 819.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. 15% of websites need less resources to load. Images take 531.2 kB which makes up the majority of the site volume.
Potential reduce by 50.6 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 50.6 kB or 79% of the original size.
Potential reduce by 39.4 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. A 187 images are well optimized though.
Potential reduce by 102.4 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 102.4 kB or 69% of the original size.
Potential reduce by 56.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. A187.com needs all CSS files to be minified and compressed as it can save up to 56.6 kB or 75% of the original size.
Number of requests can be reduced by 28 (42%)
67
39
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of A 187. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
a187.com
651 ms
bbs.999gho.com
832 ms
style_1_common.css
221 ms
style_1_forum_index.css
418 ms
common.js
617 ms
style_1_widthauto.css
401 ms
forum.js
411 ms
logging.js
420 ms
cmp.js
431 ms
forum_slide.js
607 ms
discuz_tips.js
517 ms
5f3e8fb5jw1edo142rfncj200w00w3y9.jpg
271 ms
background.png
203 ms
logo.png
443 ms
qq_login.gif
212 ms
collapsed_no.gif
217 ms
common_117_icon.jpg
233 ms
common_53_icon.jpg
338 ms
common_67_icon.jpg
431 ms
common_68_icon.jpg
443 ms
common_71_icon.gif
451 ms
common_74_icon.jpg
463 ms
common_120_icon.jpg
562 ms
common_75_icon.jpg
641 ms
common_76_icon.png
657 ms
common_101_icon.png
666 ms
common_44_icon.gif
664 ms
common_118_icon.jpg
690 ms
common_57_icon.png
769 ms
common_84_icon.jpg
855 ms
common_36_icon.gif
861 ms
common_59_icon.jpg
881 ms
common_85_icon.jpg
894 ms
common_86_icon.gif
892 ms
common_48_icon.jpg
988 ms
collapsed_yes.gif
1058 ms
security.png
1062 ms
px.png
1071 ms
newarow.gif
1074 ms
pn.png
1085 ms
nv.png
1176 ms
qmenu.png
1241 ms
nv_a.png
1247 ms
search.png
1268 ms
pt_item.png
1258 ms
chart.png
1276 ms
category_lbg.png
1362 ms
shell_v2.js
493 ms
stat.php
2842 ms
tb.png
1342 ms
loading.gif
1272 ms
212053id2d3199bbrz6rep.png
2937 ms
201810kte54tz7v8sxuigv.jpg
4374 ms
202316nzv8465w369zhwfu.jpg
2129 ms
203136tl8w3g0m28mnl78r.jpg
3008 ms
112231reesot6nh9toxyhs.jpg
3947 ms
113046h2zgzadiewh2diae.jpg
2459 ms
123820cbz996nsnswusajb.jpg
3839 ms
dot.gif
2979 ms
titlebg.png
3176 ms
bds_s_v2.js
943 ms
bdsstyle.css
257 ms
l5.gif
500 ms
stat.htm
246 ms
core.php
910 ms
9.gif
783 ms
pic.gif
4737 ms
logger.js
253 ms
scrolltop.png
226 ms
app.gif
765 ms
a187.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.
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.
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.
a187.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
a187.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
EN
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise A187.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 A187.com main page’s claimed encoding is gbk. 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.
a187.com
Open Graph description is not detected on the main page of A 187. 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: