24.8 sec in total
806 ms
23.3 sec
683 ms
Visit sem.cm now to see the best up-to-date Sem content for China and also check out these interesting facts you probably never knew about sem.cm
SEM门户网,关注SEM,分享前沿搜索引擎营销技术,让搜索营销更精准,让网络营销更有效!
Visit sem.cmWe analyzed Sem.cm page load time and found that the first response time was 806 ms and then it took 24 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 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
sem.cm performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value4.7 s
33/100
25%
Value4.3 s
76/100
10%
Value0 ms
100/100
30%
Value0.034
100/100
15%
Value4.4 s
84/100
10%
806 ms
2016 ms
665 ms
886 ms
830 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 77% of them (60 requests) were addressed to the original Sem.cm, 6% (5 requests) were made to Bdimg.share.baidu.com and 3% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (19.8 sec) relates to the external source Semplus.org.
Page size can be reduced by 421.0 kB (14%)
3.1 MB
2.7 MB
In fact, the total size of Sem.cm main page is 3.1 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. 45% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 93.8 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 12.8 kB, which is 11% 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 93.8 kB or 83% of the original size.
Potential reduce by 208.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. Sem 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 68% of the original size.
Potential reduce by 16.2 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. Sem.cm needs all CSS files to be minified and compressed as it can save up to 16.2 kB or 72% of the original size.
Number of requests can be reduced by 8 (11%)
71
63
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sem. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
sem.cm
806 ms
www.sem.cm
2016 ms
js.js
665 ms
jquery.lazyload.js
886 ms
css.css
830 ms
11.js
1884 ms
stat.php
1280 ms
hm.js
16082 ms
baidu5bu1.jpg
19840 ms
jiasijunshouke.jpg
1304 ms
3953272973.png
430 ms
10342515wyayaqdqvab3ah.jpg
19836 ms
img.gif
84 ms
bg.gif
66 ms
t.gif
67 ms
20150914112311421.jpg
147 ms
thumb_347_224_20151129104952921.jpg
106 ms
20120918123014549.gif
152 ms
20120913070147136.gif
94 ms
20150518103910380.png
127 ms
20151129104952921.jpg
160 ms
20140214062933903.jpg
141 ms
20140106024731948.png
183 ms
20140106020023262.png
166 ms
20140106013911765.jpg
195 ms
20140102010758886.jpg
177 ms
20140101100007287.jpg
181 ms
20140101122802772.jpg
197 ms
20140101120201265.jpg
237 ms
thumb_104_103_20150518103910380.png
207 ms
20160218033232688.jpg
223 ms
20151130010056554.jpg
293 ms
20151129080311902.png
271 ms
20151129040056349.jpg
233 ms
20151127093457818.png
248 ms
20151127035350668.jpg
283 ms
20150408053209923.jpg
292 ms
20151126110709460.jpg
282 ms
20141122024559558.jpg
307 ms
20141118103706185.jpg
317 ms
20130404101151539.jpg
327 ms
20121102092321910.jpg
335 ms
20131027100159464.jpg
381 ms
20131027082708252.jpg
428 ms
20130507011511169.jpg
344 ms
20130807092757513.png
369 ms
20140803112059834.png
315 ms
20140228010326825.jpg
666 ms
20130812113222813.png
4948 ms
20120903063515712.jpg
516 ms
20120914021503379.jpg
2005 ms
20120903071457778.jpg
461 ms
20120903071332149.jpg
511 ms
20150820042404879.jpg
511 ms
20140719024625448.jpg
515 ms
20140504050222484.jpg
531 ms
20120608083736740.jpg
1377 ms
20120527114236332.jpg
629 ms
20120509092407251.jpg
577 ms
20120430114512468.jpg
4981 ms
20120430114207169.bmp
699 ms
20120420124717767.jpg
732 ms
20120417122337961.jpg
994 ms
stop.png
477 ms
qq.png
211 ms
prohibit_link.gif
6523 ms
tabright1.gif
183 ms
tableft1.gif
190 ms
stat.htm
307 ms
core.php
892 ms
shell_v2.js
825 ms
9.gif
837 ms
logger.js
417 ms
bds_s_v2.js
4728 ms
app.gif
1032 ms
bdsstyle.css
310 ms
is.png
983 ms
hm.gif
1842 ms
sem.cm 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
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
sem.cm best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
sem.cm SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sem.cm can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Sem.cm 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.
sem.cm
Open Graph description is not detected on the main page of Sem. 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: