75.9 sec in total
13.7 sec
62 sec
299 ms
Welcome to otcms.com homepage info - get ready to check OTCMS best content for China right away, or after learning these important things about otcms.com
致力于文章新闻系统、文章新闻CMS、知识付费CMS、资源素材CMS、采集图片下载CMS、IDC财务管理代理系统等研发;我们坚持做简单好用人性化易操作的系统和软件(ASP/PHP/C#),傻瓜式的操作,让您在最短的时间内就可以上手并建成一个功能强大的网站。
Visit otcms.comWe analyzed Otcms.com page load time and found that the first response time was 13.7 sec and then it took 62.3 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 33 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
otcms.com performance score
name
value
score
weighting
Value5.8 s
5/100
10%
Value7.7 s
3/100
25%
Value9.0 s
14/100
10%
Value20 ms
100/100
30%
Value0.001
100/100
15%
Value6.2 s
62/100
10%
13660 ms
9360 ms
2449 ms
9081 ms
1161 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 54% of them (66 requests) were addressed to the original Otcms.com, 7% (9 requests) were made to Tianqi.2345.com and 4% (5 requests) were made to Hb.crm2.qq.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Otcms.com.
Page size can be reduced by 489.7 kB (58%)
837.5 kB
347.8 kB
In fact, the total size of Otcms.com main page is 837.5 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. 25% of websites need less resources to load. Javascripts take 464.2 kB which makes up the majority of the site volume.
Potential reduce by 94.1 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 94.1 kB or 81% of the original size.
Potential reduce by 20.7 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, OTCMS needs image optimization as it can save up to 20.7 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 278.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 278.5 kB or 60% of the original size.
Potential reduce by 96.4 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. Otcms.com needs all CSS files to be minified and compressed as it can save up to 96.4 kB or 86% of the original size.
Number of requests can be reduced by 54 (66%)
82
28
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OTCMS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
otcms.com
13660 ms
configJs.asp
9360 ms
ads.js
2449 ms
style1.css
9081 ms
navMenu11.css
1161 ms
imgTrun5.css
2938 ms
imgTrun5.js
1856 ms
share.css
3974 ms
wpa.php
563 ms
wpa.php
843 ms
wpa.php
622 ms
jquery1.8.2.js
13534 ms
common.js
10730 ms
top.js
529 ms
index.js
11016 ms
top_bg.gif
453 ms
wap2.gif
2282 ms
rss.gif
611 ms
2011010241720953.jpg
11539 ms
thumb_2016010786041801.jpg
2986 ms
thumb_2014121683119769.jpg
3340 ms
2015081161617841.png
20253 ms
thumb_2015122167917353.jpg
4336 ms
2014122383384281.png
20256 ms
2014122401100383.png
20262 ms
2015121966624721.jpg
20265 ms
2015121383051449.jpg
20268 ms
2015090861546029.png
20271 ms
2015081963848117.png
20272 ms
2015082371081009.jpg
20276 ms
2015071064020777.jpg
20278 ms
2015022401503809.gif
20279 ms
2013090142591089.png
20280 ms
2014122984659505.jpg
20280 ms
2014121683119769.jpg
20282 ms
2013061543420897.jpg
20283 ms
2011033066268313.jpg
20284 ms
2015113067251945.jpg
20262 ms
top_menuBg.gif
20261 ms
top_menuDz.gif
20262 ms
qq.png
2120 ms
top_searchDz.gif
20225 ms
top_searchBtn.gif
20225 ms
index_announ.gif
20205 ms
arrow1.gif
20204 ms
index_new.gif
20205 ms
2015111456401689.jpg
20167 ms
2015113067827793.jpg
20166 ms
2015111456434329.jpg
20166 ms
followbutton.php
2701 ms
Panel.js
4268 ms
localStorage.js
1676 ms
index.php
4856 ms
online.ww
3914 ms
stat.php
1739 ms
index_recom.gif
19843 ms
arrow2.gif
19685 ms
stat.htm
166 ms
core.php
1000 ms
OTremoteDesktop.jpg
19973 ms
followButton.css
319 ms
sso.js
2560 ms
followButton.js
2554 ms
suda.js
2555 ms
9.gif
812 ms
pic.gif
779 ms
h.js
1971 ms
OTftpBackup.jpg
20268 ms
bg_flbtn.png
22 ms
item.gif
17880 ms
app.gif
887 ms
arrow3.gif
16943 ms
contains.js
767 ms
T1B7m.XeXuXXaHNz_X-16-16.gif
245 ms
21.gif
814 ms
hm.gif
341 ms
push.js
779 ms
jquery.js
914 ms
quickfollownewstyle5.css
467 ms
follow_quick_05.js
2034 ms
r.cgi
894 ms
r.cgi
12677 ms
r.cgi
2749 ms
ta.php
3545 ms
crmqq.php
8993 ms
wpa_first_heart_beat.php
564 ms
wpa_first_heart_beat.php
586 ms
ta.php
1586 ms
wpa_first_heart_beat.php
575 ms
b.gif
869 ms
quickfollowbgnew.gif
224 ms
item2.gif
16303 ms
weixin.png
20391 ms
bottom_logo.gif
13363 ms
index.htm
11134 ms
r.cgi
891 ms
wpa_first_heart_beat.php
583 ms
popup.css
13145 ms
style.css
3906 ms
users.asp
6993 ms
robot.asp
4352 ms
popup.js
18985 ms
users.js
19977 ms
usersCenter.js
6187 ms
qqServiceTopR2.png
5628 ms
noPic.gif
6227 ms
hb.crm2.qq.com
3597 ms
wea_plugin_widget_v20150401130731.css
983 ms
jquery.js
6733 ms
common2_v20160329134747.js
1409 ms
citySelectData.js
19692 ms
smallCityName.js
3955 ms
widget_v20141205141757.js
1301 ms
tianqiplugin
1057 ms
hb.crm2.qq.com
1565 ms
qqSmall.png
791 ms
weiboSmall.png
706 ms
hb.crm2.qq.com
588 ms
hb.crm2.qq.com
581 ms
hb.crm2.qq.com
544 ms
detect2013_plugin.php
352 ms
plugin-widget.png
3539 ms
otcms.com accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
otcms.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
otcms.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
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otcms.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 Otcms.com main page’s claimed encoding is gb2312. 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.
otcms.com
Open Graph description is not detected on the main page of OTCMS. 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: