29.9 sec in total
3 sec
25.9 sec
1 sec
Click here to check amazing 18 Touch content for China. Otherwise, check out these important facts you probably never knew about 18touch.com
超好玩游戏网立足于手机游戏行业,致力于成为玩家“最值得玩家信赖的游戏媒体,最值得行业尊敬的游戏媒体”,全年365天不间断为玩家推荐好玩的手机游戏下载、丰富的游戏攻略教程和排行榜游戏。
Visit 18touch.comWe analyzed 18touch.com page load time and found that the first response time was 3 sec and then it took 26.9 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.
18touch.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value11.1 s
0/100
25%
Value10.7 s
7/100
10%
Value20 ms
100/100
30%
Value0.001
100/100
15%
Value12.4 s
14/100
10%
3017 ms
2137 ms
468 ms
765 ms
795 ms
Our browser made a total of 170 requests to load all elements on the main page. We found that 29% of them (49 requests) were addressed to the original 18touch.com, 52% (88 requests) were made to Qn.18touch.com and 5% (8 requests) were made to Api.18touch.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Qn.18touch.com.
Page size can be reduced by 1.7 MB (18%)
9.3 MB
7.6 MB
In fact, the total size of 18touch.com main page is 9.3 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. 70% of websites need less resources to load. Images take 8.3 MB which makes up the majority of the site volume.
Potential reduce by 310.3 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. This page needs HTML code to be minified as it can gain 66.7 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 310.3 kB or 86% of the original size.
Potential reduce by 879.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. Obviously, 18 Touch needs image optimization as it can save up to 879.4 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 236.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 236.1 kB or 71% of the original size.
Potential reduce by 280.5 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. 18touch.com needs all CSS files to be minified and compressed as it can save up to 280.5 kB or 82% of the original size.
Number of requests can be reduced by 25 (15%)
165
140
The browser has sent 165 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 18 Touch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
18touch.com
3017 ms
www.18touch.com
2137 ms
part.css
468 ms
bootstrap.min.css
765 ms
css.css
795 ms
topBar.css
571 ms
sea.js
574 ms
jquery.min.js
763 ms
index-top-gallery.css
702 ms
nav-game.css
869 ms
nav-game.js
871 ms
zhuanqu-mod.css
717 ms
zhuan-mod.js
805 ms
stat.php
1791 ms
bootstrap.min.js
912 ms
18touch-guanggao.js
913 ms
common.js
911 ms
Xslider.js
910 ms
carousel_L.js
908 ms
index.js
908 ms
jquery.lazyload.min.js
1044 ms
18touch-index-guangao.js
1081 ms
index-ce-nav.css
1076 ms
getScroll.js
1074 ms
icon175x175.jpeg
43 ms
1460082362826548.jpg
20297 ms
icon175x175.jpeg
45 ms
052ae55f9f4e5436d01dd1da4a2cbabf83e1071ca
461 ms
icon175x175.png
74 ms
icon175x175.png
74 ms
icon175x175.jpeg
129 ms
57038c5d136239.91926697.jpg
1060 ms
568ddd26247f24.07815716.jpg
1058 ms
55af4e2683ab10.87075172.png
1416 ms
570380e8d39907.20557848.png
1400 ms
56c6db1642af10.29407436.png
1318 ms
1435721346591995.jpg
1317 ms
56f34f155044a5.07532927.png
1624 ms
56dcdf2b225064.64947809.png
1625 ms
55e5640920d176.58163067.png
1694 ms
56c59a51471da0.25765884.png
1707 ms
5693228f962918.50455993.png
1830 ms
56cbbbec79f5b1.11399388.png
1831 ms
56dd259a048072.15399615.jpg
2005 ms
565d4b98c52462.26423170.png
2003 ms
56ef6db5d05871.24061429.png
2474 ms
569850d2d587e5.53981472.png
2089 ms
5694d6b5c0d8c5.83533159.png
2295 ms
56f34d87c9e856.41379371.png
2297 ms
56833f0686e733.32350705.jpg
2472 ms
5667d7318883e9.88742257.png
2591 ms
568384b598c441.77001967.jpg
2586 ms
1448955017507421.jpg
5455 ms
1455681128950569.png
3666 ms
1456889589896975.png
4055 ms
1447059239938781.png
4347 ms
1445336478424677.png
4740 ms
1438159741374833.png
4346 ms
1453089060191275.png
4645 ms
h1h107m-fe673d4ab9354a72b5b4dfe74504427c.png
4643 ms
1418694697856365.png
5807 ms
1421746234789978.png
5826 ms
%E6%88%91%E5%8F%ABMT2%E5%8A%A9%E6%89%8B_1.0_100.png
6023 ms
1427187756413163.png
6741 ms
1429782947252419.png
7553 ms
1432198697830661.png
6409 ms
0d48348c64c9b5477ac862347f5a42c6009420288
441 ms
0b4615b303f42c9a4610f1137da574582b341b749
442 ms
0a73194dce9ba46881343cc15dbc03a8271775328
445 ms
0d48348c64c9b5477ac862347f5a42c6009420288
444 ms
icon175x175.jpeg
23 ms
icon175x175.png
52 ms
txwb.png
672 ms
qqkj.png
777 ms
xlwb.png
892 ms
logo-transparent.png
876 ms
18touch-lazy-img.png
857 ms
zhanzhang.png
912 ms
chw.png
1145 ms
ssfls.png
1033 ms
sslhb.png
1127 ms
ss18mo.png
1135 ms
icon175x175.png
50 ms
icon175x175.jpeg
48 ms
ico_computer.png
1136 ms
new-today-title01.png
1176 ms
turn-left.png
1238 ms
turn-right.png
1335 ms
glyphicons-halflings-regular.woff
1414 ms
acs-5520-2015-12-9.png
1396 ms
aleft.png
1233 ms
imgMask.png
1342 ms
aright.png
1339 ms
starBg.png
1380 ms
star.png
1437 ms
lixz.png
1512 ms
lixz_min.png
1512 ms
ico_ccy.png
1590 ms
1455680752693790.jpg
6259 ms
1460079180302849.jpg
5651 ms
1459927307174251.jpg
5685 ms
1455866756743811.jpg
6462 ms
stat.htm
185 ms
core.php
548 ms
1459164347917484.png
5898 ms
1460017152618556.jpg
7051 ms
1458525920245629.png
7232 ms
v1_1-8_1460011137434447.jpg
6229 ms
v1_1-8_1459318854888308.jpg
6343 ms
v1_1-8_1454318912777081.jpg
6438 ms
v1_1-8_1453186577761665.jpg
6466 ms
v1_1-8_1454316074914292.jpg
6604 ms
h.js
439 ms
v1_1-8_1458208460915349.jpg
6548 ms
v1_1-8_1456378400477338.jpg
6720 ms
v1_1-8_1458033388950220.jpg
6667 ms
v1_1-8_1460080675536694.jpg
6517 ms
v1_1-8_1460081181436170.jpg
6721 ms
21.gif
849 ms
hm.gif
223 ms
getUserNewMess
1372 ms
acs-1881-2015-11-24.png
247 ms
chw-top-gallery.js
459 ms
login.js
2354 ms
webad_json
1905 ms
webad_json
2792 ms
webad_json
1898 ms
webad_json
1895 ms
webad_json
1889 ms
webad_json
4191 ms
webad_json
2337 ms
webad_json
2294 ms
57038c5d136239.91926697.jpg
6576 ms
56fb33c7511980.73000767.jpg
7107 ms
570380e8d39907.20557848.png
6779 ms
568ddd26247f24.07815716.jpg
6716 ms
56f34f155044a5.07532927.png
5673 ms
55af4e2683ab10.87075172.png
5542 ms
55e5640920d176.58163067.png
5281 ms
56c6db1642af10.29407436.png
5530 ms
566e22fd2783a8.67646418.png
5706 ms
1459153901506554.jpg
6123 ms
Proxy.html
443 ms
1458207072673824.jpg
5180 ms
jquery.min.js
8736 ms
1459318767966010.jpg
4681 ms
1459320503458884.jpg
4404 ms
1459134607315923.jpg
4571 ms
1459324410221155.jpg
4478 ms
1459134790918461.jpg
4197 ms
1458786074468556.jpg
3958 ms
1459134500514477.jpg
4053 ms
1460018673242655.jpg
4677 ms
1460081263728841.jpg
4339 ms
v1_1-8_1460106248117425.png
4392 ms
v1_1-8_1460101909593966.png
3534 ms
v1_1-8_1460085505923590.jpg
3611 ms
v1_1-8_1460085507265920.jpeg
3828 ms
1460018636885594.jpg
4145 ms
1460111824213692.jpg
4586 ms
1460108897360206.jpg
4004 ms
1460096254907963.jpg
5054 ms
1460026417400057.jpg
4270 ms
1460010746865799.jpg
4039 ms
1460085002785046.gif
9720 ms
1459996473426575.png
4748 ms
1459940100924552.gif
5223 ms
1459842805431629.jpg
4927 ms
1458801688739511.png
5565 ms
my
453 ms
18touch.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.
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
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
Links do not have a discernible name
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.
18touch.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
18touch.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 doesn't use 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 18touch.com 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 18touch.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.
18touch.com
Open Graph description is not detected on the main page of 18 Touch. 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: