32.8 sec in total
1.8 sec
30.7 sec
240 ms
Visit 0618.us now to see the best up-to-date 0618 content and also check out these interesting facts you probably never knew about 0618.us
國內著名的免費資源網站。
Visit 0618.usWe analyzed 0618.us page load time and found that the first response time was 1.8 sec and then it took 31 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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
0618.us performance score
name
value
score
weighting
Value1.6 s
93/100
10%
Value1.6 s
99/100
25%
Value1.6 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.6 s
100/100
10%
1768 ms
56 ms
1396 ms
335 ms
1422 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 58% of them (64 requests) were addressed to the original 0618.us, 5% (5 requests) were made to Pagead2.googlesyndication.com and 5% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (19.8 sec) relates to the external source Cpro.baidu.com.
Page size can be reduced by 292.6 kB (58%)
508.1 kB
215.5 kB
In fact, the total size of 0618.us main page is 508.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. 40% of websites need less resources to load. Javascripts take 346.3 kB which makes up the majority of the site volume.
Potential reduce by 64.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 64.4 kB or 81% of the original size.
Potential reduce by 6.5 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. 0618 images are well optimized though.
Potential reduce by 209.1 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 209.1 kB or 60% of the original size.
Potential reduce by 12.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. 0618.us needs all CSS files to be minified and compressed as it can save up to 12.6 kB or 77% of the original size.
Number of requests can be reduced by 77 (75%)
102
25
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 0618. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and as a result speed up the page load time.
0618.us
1768 ms
jquery.min.js
56 ms
dfFlexiGrid_inc.js
1396 ms
dfFlexiGrid.js
335 ms
styles.css
1422 ms
common.js
538 ms
jslang.js
386 ms
ajax.js
469 ms
swfobject.js
645 ms
highslide.css
743 ms
highslide-with-gallery.js
1104 ms
contact.js
1905 ms
f.js
19830 ms
stat.php
1328 ms
jquery.lazyload.js
977 ms
link-converter.js
42 ms
Std_StranJF.js
1209 ms
m.js
808 ms
show_ads.js
19 ms
brand
38 ms
track.js
459 ms
lmn.js
1507 ms
news.php
1214 ms
detail.credit
2251 ms
connect.js
1285 ms
brand
66 ms
0618
87 ms
logo2.gif
330 ms
stick_sitebro.png
484 ms
px.gif
54 ms
bg.png
337 ms
icon_top.png
333 ms
icon_email.gif
334 ms
icon_oicq.png
339 ms
icon_msn.gif
343 ms
icon_bottom.png
359 ms
close_announce.gif
663 ms
close_left_sidebar.gif
673 ms
close_right_sidebar.gif
670 ms
increase_size.gif
665 ms
reduction_size.gif
688 ms
small_screen.gif
708 ms
default_screen.gif
1004 ms
wide_screen.gif
1010 ms
full_screen.gif
2013 ms
zh-cn.gif
1010 ms
zh-tw.gif
1004 ms
en.gif
1033 ms
vn.gif
1321 ms
logo.png
1795 ms
1.png
1346 ms
rss.png
1384 ms
2.png
1385 ms
3.png
1641 ms
5.png
1728 ms
6.png
1738 ms
4.png
1744 ms
cat.png
1952 ms
doubleleft.gif
2059 ms
singleright.gif
2055 ms
doubleright.gif
2073 ms
but-rss.gif
2126 ms
css.gif
2285 ms
xhtml10.gif
2357 ms
stat.htm
1392 ms
core.php
1052 ms
9.gif
1069 ms
pic.gif
1785 ms
top_m.png
313 ms
top_lr.png
317 ms
login_bg.png
338 ms
submit.png
357 ms
rchm
797 ms
rchm
987 ms
rchm
412 ms
xuanfu_close.png
539 ms
rchm
534 ms
menu_m.png
342 ms
menu_lr.png
344 ms
panel_bg2.png
335 ms
title_bg.png
349 ms
list.gif
349 ms
ca-pub-7335360126327110.js
114 ms
zrt_lookup.html
112 ms
show_ads_impl.js
49 ms
app.gif
755 ms
ads
188 ms
osd.js
23 ms
ads
201 ms
ads
227 ms
bottom.png
350 ms
footer.png
476 ms
TrojanInspect.aspx
3365 ms
abg.js
71 ms
m_js_controller.js
30 ms
favicon
80 ms
s
14 ms
googlelogo_color_112x36dp.png
38 ms
nessie_icon_tiamat_white.png
22 ms
x_button_blue2.png
27 ms
j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js
6 ms
snippetcacher.php
1578 ms
tdflagx1.gif
380 ms
grey.gif
182 ms
drop-shadow.png
174 ms
o.htm
2012 ms
zoomout.cur
174 ms
loader.white.gif
313 ms
wh.js
727 ms
ac.js
523 ms
fp.htm
513 ms
0618.us 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
<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.
0618.us best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
0618.us 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
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 0618.us can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Chinese language. Our system also found out that 0618.us 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.
0618.us
Open Graph description is not detected on the main page of 0618. 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: