53.7 sec in total
5.5 sec
47.7 sec
512 ms
Welcome to m.fontke.com homepage info - get ready to check M Fontke best content for China right away, or after learning these important things about m.fontke.com
字客网是全球知名的字体下载与分享网站,齐全的中文,日文,韩文,英文,图标,美术设计,毛笔,钢笔,手写,书法字体大全,提供找字体,字体识别,字体下载,在线字体预览,字体转换,字体设计等服务。
Visit m.fontke.comWe analyzed M.fontke.com page load time and found that the first response time was 5.5 sec and then it took 48.2 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.
m.fontke.com performance score
5525 ms
378 ms
682 ms
684 ms
688 ms
Our browser made a total of 180 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original M.fontke.com, 18% (33 requests) were made to En.fontke.com and 1% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Statics.fontke.com.
Page size can be reduced by 436.3 kB (18%)
2.5 MB
2.0 MB
In fact, the total size of M.fontke.com main page is 2.5 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 2.1 MB which makes up the majority of the site volume.
Potential reduce by 108.2 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 108.2 kB or 82% of the original size.
Potential reduce by 161.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. M Fontke images are well optimized though.
Potential reduce by 105.8 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 105.8 kB or 65% of the original size.
Potential reduce by 60.9 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. M.fontke.com needs all CSS files to be minified and compressed as it can save up to 60.9 kB or 79% of the original size.
Number of requests can be reduced by 21 (12%)
177
156
The browser has sent 177 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M Fontke. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
en.fontke.com
5525 ms
base.css
378 ms
base.css
682 ms
jquery-ui.min.css
684 ms
lxslider.css
688 ms
index.css
729 ms
index.css
741 ms
jquery-1.8.3.min.js
1146 ms
base.js
1043 ms
jquery-ui.min.js
1056 ms
jquery.kinMaxShow-1.1.min.js
1050 ms
jqColorPicker.min.js
1103 ms
lxslider.js
2368 ms
weixin.jpg
9443 ms
base.png
1018 ms
hlbg.gif
373 ms
20160627171428420.jpeg
588 ms
20160627171448134.jpeg
1862 ms
20160627171732567.jpg
1743 ms
20160627171311470.png
777 ms
20160627171522692.jpeg
1511 ms
in-logo.png
8461 ms
577716705f859.jpg
11076 ms
56b3f6fb0f41b.jpg
10170 ms
57984b53351b2.jpg
11511 ms
57a04e0b9d136.png
11273 ms
5745444ca8660.jpg
11216 ms
574ea597dcf5e.png
13200 ms
572966c7b10aa.png
11761 ms
5745202c6e6ef.png
11921 ms
57455ee30ee78.jpg
11624 ms
574545f423431.png
12868 ms
280x210.png
13093 ms
280x210.png
13085 ms
280x210.png
16299 ms
280x210.png
14427 ms
280x210.png
14593 ms
280x210.png
13445 ms
280x210.png
17502 ms
280x210.png
15109 ms
580.png
13790 ms
580.png
15392 ms
580.png
15446 ms
580.png
18335 ms
580.png
15452 ms
580.png
15736 ms
580.png
15785 ms
580.png
16498 ms
580.png
16669 ms
580.png
19749 ms
580.png
17362 ms
580.png
18197 ms
580.png
17015 ms
580.png
17362 ms
580.png
17711 ms
580.png
17711 ms
user_info
1365 ms
hfbg.gif
1122 ms
nlbg.gif
1353 ms
indbg.gif
1514 ms
cy-home.png
2097 ms
font-firm.png
1733 ms
cy-maker.png
1835 ms
font-designer.png
1893 ms
mbbg.png
2055 ms
newbg.gif
2104 ms
guest.png
2179 ms
11.0.1.js
2953 ms
push.js
2464 ms
hm.js
2299 ms
piwik.js
19674 ms
hm.gif
346 ms
ab77b6ea7f3fbf79.js
2579 ms
error.html
1771 ms
ui-bg_flat_75_ffffff_40x100.png
387 ms
ui-bg_glass_75_e6e6e6_1x400.png
376 ms
580.png
9395 ms
580.png
8637 ms
580.png
7897 ms
580.png
8439 ms
580.png
7761 ms
580.png
7149 ms
580.png
7035 ms
580.png
7057 ms
580.png
7009 ms
580.png
7585 ms
580.png
6774 ms
580.png
6659 ms
580.png
7338 ms
580.png
16869 ms
591d67b4a1f96.png
8646 ms
56b45cd988c6b.png
7986 ms
573c2f3805bae.png
8706 ms
573d2027e1a85.png
6523 ms
573c1a1ac5bc8.png
5717 ms
573c0c78a4f13.png
6148 ms
573c11a43eed3.png
6010 ms
5742a9bbcff10.jpg
7021 ms
5742a65e3e70f.jpg
6899 ms
574e5d92ecc0f.png
9358 ms
574911c553041.jpg
7503 ms
5749355f6989f.jpg
7545 ms
57427f5f7898c.jpg
6322 ms
574912e468410.jpg
6335 ms
56b30378ab8e7.png
9076 ms
5736f98b99431.png
7055 ms
573c1f1b44919.png
6644 ms
56b2f6d23e641.png
6672 ms
573d124208b9e.png
6772 ms
573c1110e2a48.png
6876 ms
576118d51d286.png
6713 ms
5742a4ebb6e0e.jpg
7453 ms
5742ac41177ed.jpg
7754 ms
574944890db46.jpg
6808 ms
574275d2ea26e.jpg
7078 ms
57426f8deacc3.png
7507 ms
5749164525aaf.jpg
7178 ms
5742aef12144f.png
7446 ms
56b2a865467d6.png
7247 ms
59182d046c35c.png
8565 ms
56b2a3b483897.png
6881 ms
5919d2de6e953.png
7262 ms
56b2a756c9958.png
6836 ms
56b2a265a9abe.png
9561 ms
56b2a684ac770.png
6358 ms
5743efc3a71b1.jpg
6114 ms
5916408a54c3d.jpg
6363 ms
573c54391f7d8.jpg
6824 ms
5749401d41aab.jpg
5759 ms
5743f20403bb9.jpg
5883 ms
5743ef3cc86cb.jpg
7464 ms
5743efd8ca11d.jpg
5544 ms
56b2f92e5a0b7.png
5740 ms
56b2f4e65003e.png
5417 ms
573c53c468f61.png
6047 ms
56b2a6083046f.png
5947 ms
56b2f8724cb8f.png
4953 ms
573c33ba87910.png
6133 ms
56b3034611b56.png
5380 ms
5916befc3fbbd.jpg
6399 ms
5742a12e289d7.jpg
6462 ms
5749446e01c13.jpg
5728 ms
57493d6977f38.jpg
6553 ms
57493d318a79a.jpg
7910 ms
5742b75d65a96.png
7084 ms
56b2eddaa4007.png
6311 ms
5736f8eb88971.png
5648 ms
5712e8fd7c875.png
7356 ms
56b305d97e2dc.png
5644 ms
591d7c8ca3e10.png
6359 ms
56b2e91a1e819.png
5751 ms
56b2ffc42e9a5.png
5649 ms
574e82f071a9f.jpg
6271 ms
57493e8721169.jpg
5830 ms
57ad3992e4754.gif
6143 ms
57464776c30bf.jpg
6677 ms
58c9e2c41684c.png
9536 ms
5746462ecdff3.png
9377 ms
58ccf41ec196d.jpg
6363 ms
574646d60f9f6.jpg
8091 ms
58c661aa66939.jpg
8989 ms
57ad391f81a7a.gif
7987 ms
57624afea0e42.png
5999 ms
585b73d6e624e.jpg
7025 ms
57634a550ffec.jpeg
7172 ms
58b543b8ecfc6.jpg
7692 ms
57624ef24419f.jpeg
7399 ms
57634c78c2b92.jpeg
7236 ms
586e16f42a2b7.jpg
6991 ms
268751_128.jpg
7031 ms
139397_128.jpg
7096 ms
278086_128.jpg
7002 ms
279663_128.jpg
7070 ms
279355_128.jpg
6602 ms
beian.png
6495 ms
fontke-footer-logo.png
6531 ms
fonturl-footer-logo.png
6021 ms
likefont-footer-logo.png
6000 ms
fontren-footer-logo.png
5824 ms
cta-footer-logo.png
5733 ms
m.fontke.com SEO score
ZH
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise M.fontke.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that M.fontke.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.
m.fontke.com
Open Graph description is not detected on the main page of M Fontke. 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: