Tools & Wizards About Us
formkid.com screenshot

Report Summary

  • 0

    Performance

  • 49

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 68

    SEO

    Google-friendlier than
    28% of websites

formkid.com

Page Load Speed

31 sec in total

First Response

868 ms

Resources Loaded

29.8 sec

Page Rendered

312 ms

formkid.com screenshot

About Website

Visit formkid.com now to see the best up-to-date Formkid content and also check out these interesting facts you probably never knew about formkid.com

Visit formkid.com

Key Findings

We analyzed Formkid.com page load time and found that the first response time was 868 ms and then it took 30.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 60 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

formkid.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value18.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value23.6 s

0/100

25%

SI (Speed Index)

Value26.5 s

0/100

10%

TBT (Total Blocking Time)

Value13,180 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.898

3/100

15%

TTI (Time to Interactive)

Value32.9 s

0/100

10%

Network Requests Diagram

www.formkid.com

868 ms

style.css

472 ms

idangerous.swiper.css

475 ms

responsive.css

479 ms

jquerys.js

695 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 31% of them (33 requests) were addressed to the original Formkid.com, 56% (59 requests) were made to Aqmc.edu.cn and 8% (8 requests) were made to Txktty.top. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source 4f34f4b.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 69.0 kB (16%)

Content Size

444.8 kB

After Optimization

375.8 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Formkid.com main page is 444.8 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. 60% of websites need less resources to load. Javascripts take 309.0 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 64.5 kB

  • Original 86.3 kB
  • After minification 83.3 kB
  • After compression 21.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. 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 64.5 kB or 75% of the original size.

JavaScript Optimization

-1%

Potential reduce by 3.8 kB

  • Original 309.0 kB
  • After minification 309.0 kB
  • After compression 305.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 656 B

  • Original 49.5 kB
  • After minification 49.5 kB
  • After compression 48.8 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. Formkid.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 39 (87%)

Requests Now

45

After Optimization

6

  • AJAX
  • JavaScript
  • CSS

The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Formkid. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.formkid.com

www.formkid.com

868 ms

style.css

style.css

472 ms

idangerous.swiper.css

idangerous.swiper.css

475 ms

responsive.css

responsive.css

479 ms

jquerys.js

jquerys.js

695 ms

jquery-migrate.min.js

jquery-migrate.min.js

486 ms

shengji.js

shengji.js

492 ms

ag.js

ag.js

674 ms

_sitegray_d.css

_sitegray_d.css

729 ms

_sitegray.js

_sitegray.js

733 ms

index.vsb.css

index.vsb.css

746 ms

counter.js

counter.js

752 ms

dynclicks.js

dynclicks.js

923 ms

openlink.js

openlink.js

948 ms

base64.js

base64.js

984 ms

jquery-latest.min.js

jquery-latest.min.js

1211 ms

vue.js

vue.js

1701 ms

bluebird.min.js

bluebird.min.js

1240 ms

axios.js

axios.js

1175 ms

polyfill.js

polyfill.js

1221 ms

token.js

token.js

1237 ms

index.css

index.css

1659 ms

index.js

index.js

2169 ms

public.js

public.js

1478 ms

centerCutImg.js

centerCutImg.js

1497 ms

ajax.js

ajax.js

1502 ms

idangerous.swiper.min.js

idangerous.swiper.min.js

1537 ms

idangerous.swiper.progress.min.js

idangerous.swiper.progress.min.js

1549 ms

videobanner.js

videobanner.js

1565 ms

common.js

common.js

1705 ms

style.js

style.js

1760 ms

js-sdk-pro.min.js

js-sdk-pro.min.js

898 ms

txktty.top

txktty.top

247 ms

push.js

push.js

660 ms

11.0.1.js

11.0.1.js

823 ms

matomo.js

matomo.js

20490 ms

jquery-3.5.1.js

jquery-3.5.1.js

37 ms

tinstall_inner_d.min.js

tinstall_inner_d.min.js

49 ms

mobile-detect.min.js

mobile-detect.min.js

25 ms

js

js

60 ms

chunk-vendors.32ed9b46.css

chunk-vendors.32ed9b46.css

79 ms

index.decfda6a.css

index.decfda6a.css

27 ms

chunk-vendors.c2c79571.js

chunk-vendors.c2c79571.js

33 ms

index.d0d78cf8.js

index.d0d78cf8.js

57 ms

ab77b6ea7f3fbf79.js

ab77b6ea7f3fbf79.js

245 ms

datainput.jsp

datainput.jsp

5913 ms

a_logo.png

a_logo.png

20443 ms

xiaoxun_img.png

xiaoxun_img.png

20401 ms

nav_decoration_img1.jpg

nav_decoration_img1.jpg

20293 ms

guoqng.jpg

guoqng.jpg

19970 ms

weixintupian_20231117093217.jpg

weixintupian_20231117093217.jpg

19970 ms

kxdlquan.jpg

kxdlquan.jpg

19969 ms

banner1.jpg

banner1.jpg

19969 ms

20180910125451.jpg

20180910125451.jpg

19968 ms

8B7BD12F993763B66EB5AA462A2_2BD75AE1_4545E.jpg

8B7BD12F993763B66EB5AA462A2_2BD75AE1_4545E.jpg

19969 ms

21663786D78FBC66EFD0FE64549_F575E7AD_597D5.jpg

21663786D78FBC66EFD0FE64549_F575E7AD_597D5.jpg

19968 ms

4AE7F0A83858C2FA95A9FF5382F_5DDA1873_4E26E.jpg

4AE7F0A83858C2FA95A9FF5382F_5DDA1873_4E26E.jpg

19969 ms

15323EA56C04308172CD9922891_215A87CD_4EC6D.jpg

15323EA56C04308172CD9922891_215A87CD_4EC6D.jpg

19968 ms

B576D79BFBC0CE6634803182EC4_16BC6986_192EA.jpg

B576D79BFBC0CE6634803182EC4_16BC6986_192EA.jpg

19968 ms

ico_zt1.jpg

ico_zt1.jpg

19968 ms

r_rtkxg.png

r_rtkxg.png

19968 ms

ico_zt5.jpg

ico_zt5.jpg

19967 ms

12.jpg

12.jpg

19967 ms

ico_zt9.jpg

ico_zt9.jpg

19966 ms

ico_zt7.jpg

ico_zt7.jpg

19966 ms

ico_zt2.jpg

ico_zt2.jpg

19967 ms

1.jpg

1.jpg

19966 ms

ico_zt11.jpg

ico_zt11.jpg

19966 ms

ico_zt16.jpg

ico_zt16.jpg

19965 ms

pic4.jpg

pic4.jpg

19965 ms

5057AC9BC63AC4E0C5C74DFD0D0_E0C02FB3_3BE79.jpg

5057AC9BC63AC4E0C5C74DFD0D0_E0C02FB3_3BE79.jpg

19965 ms

footerlogo.png

footerlogo.png

19966 ms

foot-xx.png

foot-xx.png

19965 ms

weixin_code.jpg

weixin_code.jpg

19965 ms

33AE8B55E93618A873EB629BBDC_5E0E2CF0_12AE.png

33AE8B55E93618A873EB629BBDC_5E0E2CF0_12AE.png

19965 ms

zhxy.png

zhxy.png

19965 ms

B0FDB0737982A78E1796B7735BB_4763B7E6_1405.png

B0FDB0737982A78E1796B7735BB_4763B7E6_1405.png

19964 ms

jztp.gif

jztp.gif

19964 ms

www.formkid.com

www.formkid.com

488 ms

header_background.jpg

header_background.jpg

19726 ms

search_icon.png

search_icon.png

19704 ms

nav_down_background.png

nav_down_background.png

19686 ms

swiper-prev.png

swiper-prev.png

19677 ms

swiper-next.png

swiper-next.png

20467 ms

icon_yz.png

icon_yz.png

20430 ms

section-bg2.jpg

section-bg2.jpg

20428 ms

icon_tz.png

icon_tz.png

20413 ms

icon_zb_h.png

icon_zb_h.png

20372 ms

icon_yz2.png

icon_yz2.png

20212 ms

icon_jy.png

icon_jy.png

20205 ms

icon_xy.png

icon_xy.png

20201 ms

icon_xs_h.png

icon_xs_h.png

20179 ms

icon_zt.png

icon_zt.png

20153 ms

swiper-left.png

swiper-left.png

20119 ms

pic2.jpg

pic2.jpg

19962 ms

swiper-right.png

swiper-right.png

19961 ms

pic3.jpg

pic3.jpg

19945 ms

pic5.jpg

pic5.jpg

19929 ms

mtjj.png

mtjj.png

19896 ms

icon_qq.png

icon_qq.png

19869 ms

clock_icon.png

clock_icon.png

19705 ms

kjrk.png

kjrk.png

19696 ms

li4.png

li4.png

19684 ms

2023071311.png

2023071311.png

19678 ms

2023071322.png

2023071322.png

19640 ms

to-bot.png

to-bot.png

19620 ms

Accessibility Review

formkid.com accessibility score

49

Accessibility Issues

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

formkid.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

formkid.com SEO score

68

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

High

robots.txt is not valid

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

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Formkid.com 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), while the claimed language is English. Our system also found out that Formkid.com 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.

Social Sharing Optimization

formkid.com

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