Tools & Wizards About Us
fontke.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

fontke.com

字体下载,字体大全,免费字体下载,在线字体|字客网

Page Load Speed

51.6 sec in total

First Response

1.4 sec

Resources Loaded

49.6 sec

Page Rendered

561 ms

fontke.com screenshot

About Website

Welcome to fontke.com homepage info - get ready to check Fontke best content for China right away, or after learning these important things about fontke.com

字客网是全球知名的字体下载与分享网站,齐全的中文,日文,韩文,英文,图标,美术设计,毛笔,钢笔,手写,书法字体大全,提供找字体,字体识别,字体下载,在线字体预览,字体转换,字体设计等服务。

Visit fontke.com

Key Findings

We analyzed Fontke.com page load time and found that the first response time was 1.4 sec and then it took 50.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 31 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

fontke.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value980 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value6.6 s

57/100

10%

Network Requests Diagram

fontke.com

1400 ms

www.fontke.com

4486 ms

jquery-1.8.3.min.js

2623 ms

jquery-ui.min.js

1348 ms

jquery.kinMaxShow-1.1.min.js

898 ms

Our browser made a total of 142 requests to load all elements on the main page. We found that 68% of them (96 requests) were addressed to the original Fontke.com, 6% (8 requests) were made to Pos.baidu.com and 5% (7 requests) were made to Cpro.baidustatic.com. The less responsive or slowest element that took the longest time to load (20.1 sec) belongs to the original domain Fontke.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 523.4 kB (37%)

Content Size

1.4 MB

After Optimization

890.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fontke.com main page is 1.4 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. 50% of websites need less resources to load. Images take 738.4 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 75.2 kB

  • Original 96.7 kB
  • After minification 91.7 kB
  • After compression 21.5 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 75.2 kB or 78% of the original size.

Image Optimization

-13%

Potential reduce by 98.1 kB

  • Original 738.4 kB
  • After minification 640.3 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, Fontke needs image optimization as it can save up to 98.1 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-58%

Potential reduce by 293.3 kB

  • Original 508.2 kB
  • After minification 481.9 kB
  • After compression 214.9 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 293.3 kB or 58% of the original size.

CSS Optimization

-81%

Potential reduce by 56.8 kB

  • Original 70.2 kB
  • After minification 65.5 kB
  • After compression 13.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. Fontke.com needs all CSS files to be minified and compressed as it can save up to 56.8 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (38%)

Requests Now

106

After Optimization

66

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 24 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fontke.com

fontke.com

1400 ms

www.fontke.com

www.fontke.com

4486 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

2623 ms

jquery-ui.min.js

jquery-ui.min.js

1348 ms

jquery.kinMaxShow-1.1.min.js

jquery.kinMaxShow-1.1.min.js

898 ms

jqColorPicker.min.js

jqColorPicker.min.js

1350 ms

lxslider.js

lxslider.js

3846 ms

base.js

base.js

1342 ms

jquery-ui.min.css

jquery-ui.min.css

3488 ms

jqColorPicker.css

jqColorPicker.css

1804 ms

lxslider.css

lxslider.css

1803 ms

base.css

base.css

2272 ms

index.css

index.css

2273 ms

stats

stats

15764 ms

adsbygoogle.js

adsbygoogle.js

13 ms

c.js

c.js

1043 ms

hlbg.gif

hlbg.gif

492 ms

base.png

base.png

1865 ms

in-logo.jpg

in-logo.jpg

939 ms

56fa428d3457a.png

56fa428d3457a.png

7552 ms

56f4ea74ee323.jpg

56f4ea74ee323.jpg

11840 ms

5705c8f0792c7.png

5705c8f0792c7.png

6385 ms

56b44c1b46707.jpg

56b44c1b46707.jpg

20100 ms

56b3120de8267.jpg

56b3120de8267.jpg

18448 ms

56b30e803bc51.jpg

56b30e803bc51.jpg

15464 ms

56e2890c1db3d.png

56e2890c1db3d.png

20100 ms

56e28a467dcf9.jpg

56e28a467dcf9.jpg

17410 ms

56e27f6e60b5a.png

56e27f6e60b5a.png

20099 ms

56b30ebbe9d14.png

56b30ebbe9d14.png

20100 ms

56b314a21a8ff.png

56b314a21a8ff.png

20101 ms

56e283c507192.png

56e283c507192.png

20101 ms

280x224.png

280x224.png

20102 ms

280x224.png

280x224.png

20102 ms

280x224.png

280x224.png

20103 ms

280x224.png

280x224.png

20102 ms

280x224.png

280x224.png

20103 ms

280x224.png

280x224.png

20103 ms

280x224.png

280x224.png

20103 ms

280x224.png

280x224.png

20103 ms

580.png

580.png

20103 ms

580.png

580.png

20103 ms

580.png

580.png

20104 ms

580.png

580.png

20103 ms

580.png

580.png

20104 ms

580.png

580.png

20104 ms

580.png

580.png

20104 ms

580.png

580.png

20104 ms

580.png

580.png

20105 ms

580.png

580.png

20104 ms

cy-home.jpg

cy-home.jpg

20105 ms

nophoto.gif

nophoto.gif

20104 ms

user_info

user_info

20095 ms

56b2a3143a20c.png

56b2a3143a20c.png

19630 ms

56b1d14943105.png

56b1d14943105.png

19899 ms

56b2a265a9abe.png

56b2a265a9abe.png

19588 ms

56b2a3b483897.png

56b2a3b483897.png

15104 ms

cy-maker.jpg

cy-maker.jpg

15278 ms

561e16653d8ae.jpg

561e16653d8ae.jpg

9361 ms

ca-pub-5930385669586631.js

ca-pub-5930385669586631.js

72 ms

zrt_lookup.html

zrt_lookup.html

63 ms

show_ads_impl.js

show_ads_impl.js

63 ms

wcgm

wcgm

826 ms

wcgm

wcgm

913 ms

ads

ads

271 ms

wcgm

wcgm

973 ms

osd.js

osd.js

124 ms

hm.js

hm.js

19872 ms

push.js

push.js

857 ms

piwik.js

piwik.js

2401 ms

m_js_controller.js

m_js_controller.js

39 ms

abg.js

abg.js

53 ms

ads

ads

250 ms

favicon

favicon

80 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

49 ms

mobile_unified_button_icon_white.png

mobile_unified_button_icon_white.png

40 ms

s

s

27 ms

x_button_blue2.png

x_button_blue2.png

11 ms

Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js

Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js

5 ms

css

css

104 ms

favicon

favicon

116 ms

wcgm

wcgm

1172 ms

PuwvqkdbcqU-fCZ9Ed-b7S3USBnSvpkopQaUR-2r7iU.ttf

PuwvqkdbcqU-fCZ9Ed-b7S3USBnSvpkopQaUR-2r7iU.ttf

57 ms

wcgm

wcgm

583 ms

wcgm

wcgm

554 ms

sync.htm

sync.htm

506 ms

ctm3.js

ctm3.js

521 ms

activeview

activeview

17 ms

adx.php

adx.php

872 ms

reduce_bd-logo1_oper.png

reduce_bd-logo1_oper.png

533 ms

sync_pos.htm

sync_pos.htm

477 ms

0f000D3NcMDJfa3hkUN920.jpg

0f000D3NcMDJfa3hkUN920.jpg

812 ms

sync2r.htm

sync2r.htm

1573 ms

closefeedback.min.js

closefeedback.min.js

268 ms

reduce_promotion_oper.png

reduce_promotion_oper.png

477 ms

bd_logo.png

bd_logo.png

489 ms

bg_rb.png

bg_rb.png

501 ms

561e251eeda40.jpg

561e251eeda40.jpg

6109 ms

56b15afdb8ffe.jpg

56b15afdb8ffe.jpg

4907 ms

561e25897bd6d.jpg

561e25897bd6d.jpg

4917 ms

56a719243d091.jpg

56a719243d091.jpg

13688 ms

56b19c609de3d.jpg

56b19c609de3d.jpg

1861 ms

561e263f8b17a.jpg

561e263f8b17a.jpg

3671 ms

56c01b2a099b2.png

56c01b2a099b2.png

3992 ms

56b2f4c2b605c.png

56b2f4c2b605c.png

5388 ms

56b303eb696b6.png

56b303eb696b6.png

6556 ms

56c285b456e63.png

56c285b456e63.png

5935 ms

56b3035d5b50e.png

56b3035d5b50e.png

4053 ms

56b2f5aa28f80.png

56b2f5aa28f80.png

5740 ms

56b302505cae1.png

56b302505cae1.png

4427 ms

56b2ea5cdcaac.png

56b2ea5cdcaac.png

4787 ms

56b2ff5692452.png

56b2ff5692452.png

5142 ms

56b2ffc42e9a5.png

56b2ffc42e9a5.png

5946 ms

56b305d97e2dc.png

56b305d97e2dc.png

6392 ms

56b2eddaa4007.png

56b2eddaa4007.png

10406 ms

56b2e91a1e819.png

56b2e91a1e819.png

7933 ms

56c2c134b6ae7.jpg

56c2c134b6ae7.jpg

7600 ms

280x224.png

280x224.png

13291 ms

280x224.png

280x224.png

10821 ms

280x224.png

280x224.png

11037 ms

280x224.png

280x224.png

17659 ms

280x224.png

280x224.png

14837 ms

280x224.png

280x224.png

19984 ms

280x224.png

280x224.png

13905 ms

280x224.png

280x224.png

19984 ms

no.gif

no.gif

18003 ms

128990_128.jpg

128990_128.jpg

14259 ms

126703_128.jpg

126703_128.jpg

14597 ms

128518_128.jpg

128518_128.jpg

14250 ms

128293_128.jpg

128293_128.jpg

14616 ms

hfbg.gif

hfbg.gif

13991 ms

nlbg.gif

nlbg.gif

14309 ms

indbg.gif

indbg.gif

15559 ms

mbbg.png

mbbg.png

14883 ms

newbg.gif

newbg.gif

14963 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

14664 ms

ui-bg_glass_75_e6e6e6_1x400.png

ui-bg_glass_75_e6e6e6_1x400.png

14417 ms

lx_loader.gif

lx_loader.gif

14876 ms

o.htm

o.htm

1047 ms

ui

ui

95 ms

wh.js

wh.js

782 ms

ac.js

ac.js

542 ms

fp.htm

fp.htm

590 ms

Accessibility Review

fontke.com accessibility score

76

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

fontke.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

fontke.com SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fontke.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 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.

Social Sharing Optimization

fontke.com

Open Graph description is not detected on the main page of 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: