Tools & Wizards About Us
kiddingkid.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

kiddingkid.com

Funny Stuff | Funny News | Weird News - KiddingKid.com

Page Load Speed

2.3 sec in total

First Response

219 ms

Resources Loaded

2 sec

Page Rendered

114 ms

kiddingkid.com screenshot

About Website

Welcome to kiddingkid.com homepage info - get ready to check Kidding Kid best content right away, or after learning these important things about kiddingkid.com

Funny Stuff, Funny News, Weird News, Weird Facts, Weird People, Funny Top Ten Lists are the things we focus on KiddingKid.com. Have unlimited entertainment!

Visit kiddingkid.com

Key Findings

We analyzed Kiddingkid.com page load time and found that the first response time was 219 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

kiddingkid.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

20/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value310 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0.335

34/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

kiddingkid.com

219 ms

kiddingkid.com

838 ms

wp-emoji-release.min.js

262 ms

theme-my-login.css

286 ms

css

45 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 81% of them (39 requests) were addressed to the original Kiddingkid.com, 10% (5 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (838 ms) belongs to the original domain Kiddingkid.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 571.3 kB (51%)

Content Size

1.1 MB

After Optimization

557.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 42.2 kB

  • Original 52.3 kB
  • After minification 49.5 kB
  • After compression 10.0 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 42.2 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 4.1 kB

  • Original 256.1 kB
  • After minification 251.9 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. Kidding Kid images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 450.1 kB

  • Original 727.8 kB
  • After minification 727.7 kB
  • After compression 277.6 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 450.1 kB or 62% of the original size.

CSS Optimization

-81%

Potential reduce by 74.8 kB

  • Original 92.1 kB
  • After minification 83.7 kB
  • After compression 17.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. Kiddingkid.com needs all CSS files to be minified and compressed as it can save up to 74.8 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (75%)

Requests Now

40

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kiddingkid.com

kiddingkid.com

219 ms

kiddingkid.com

kiddingkid.com

838 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

262 ms

theme-my-login.css

theme-my-login.css

286 ms

css

css

45 ms

style.css

style.css

287 ms

wp-show-posts-min.css

wp-show-posts-min.css

286 ms

unsemantic-grid.min.css

unsemantic-grid.min.css

287 ms

style.min.css

style.min.css

383 ms

mobile.min.css

mobile.min.css

287 ms

font-awesome-essentials.min.css

font-awesome-essentials.min.css

311 ms

style-min.css

style-min.css

311 ms

unsemantic-grid-responsive-tablet.css

unsemantic-grid-responsive-tablet.css

404 ms

sticky.min.css

sticky.min.css

312 ms

offside.min.css

offside.min.css

382 ms

jquery.js

jquery.js

596 ms

jquery-migrate.min.js

jquery-migrate.min.js

408 ms

api.js

api.js

35 ms

themed-profiles.js

themed-profiles.js

408 ms

js

js

59 ms

vertical.css

vertical.css

408 ms

sticky.min.js

sticky.min.js

384 ms

offside.min.js

offside.min.js

405 ms

menu.min.js

menu.min.js

406 ms

a11y.min.js

a11y.min.js

406 ms

dropdown.min.js

dropdown.min.js

409 ms

navigation-search.min.js

navigation-search.min.js

478 ms

back-to-top.min.js

back-to-top.min.js

499 ms

imagesloaded.min.js

imagesloaded.min.js

500 ms

masonry.min.js

masonry.min.js

600 ms

jquery.masonry.min.js

jquery.masonry.min.js

588 ms

scripts.min.js

scripts.min.js

592 ms

wp-embed.min.js

wp-embed.min.js

603 ms

recaptcha__en.js

recaptcha__en.js

123 ms

kiddingkid-logo5.png

kiddingkid-logo5.png

164 ms

The-One-Ring-300-300x300.png

The-One-Ring-300-300x300.png

348 ms

water-slide-tester.jpg

water-slide-tester.jpg

164 ms

320px-Church_Our_Lady_Mary_Zion_Axum_Ethio.jpg

320px-Church_Our_Lady_Mary_Zion_Axum_Ethio.jpg

164 ms

laughter-death.jpg

laughter-death.jpg

164 ms

weird-stuff-found-stuffed-in-womens-bra-300x300.jpg

weird-stuff-found-stuffed-in-womens-bra-300x300.jpg

164 ms

Ablutophobia-300x300.jpg

Ablutophobia-300x300.jpg

255 ms

fruit-and-vegetable-holder.jpg

fruit-and-vegetable-holder.jpg

255 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

94 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

95 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

108 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

122 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

121 ms

generatepress.ttf

generatepress.ttf

197 ms

Accessibility Review

kiddingkid.com accessibility score

88

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

High

ARIA IDs are not unique

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.

Best Practices

kiddingkid.com best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

kiddingkid.com SEO score

99

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kiddingkid.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Kiddingkid.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

kiddingkid.com

Open Graph data is detected on the main page of Kidding Kid. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: