Tools & Wizards About Us

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

how-to-be-funny.com

How to Be Funny - How to Tell Jokes

Page Load Speed

2.2 sec in total

First Response

46 ms

Resources Loaded

555 ms

Page Rendered

1.6 sec

About Website

Click here to check amazing How To Be Funny content. Otherwise, check out these important facts you probably never knew about how-to-be-funny.com

Learn how to be funny, tell jokes, and develop your wit with this course!

Visit how-to-be-funny.com

Key Findings

We analyzed How-to-be-funny.com page load time and found that the first response time was 46 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

how-to-be-funny.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value43.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,480 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.038

100/100

15%

TTI (Time to Interactive)

Value7.9 s

43/100

10%

Network Requests Diagram

how-to-be-funny.com

46 ms

styles.css

76 ms

footerbar.css

47 ms

border_topleft.png

64 ms

spacer.gif

154 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original How-to-be-funny.com, 90% (46 requests) were made to Cdn.selfdevelopment.net and 4% (2 requests) were made to E.selfdevelopment.net. The less responsive or slowest element that took the longest time to load (414 ms) relates to the external source Cdn.selfdevelopment.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 190.5 kB (38%)

Content Size

496.1 kB

After Optimization

305.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of How-to-be-funny.com main page is 496.1 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. 25% of websites need less resources to load. Images take 275.6 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 85.2 kB

  • Original 98.0 kB
  • After minification 64.6 kB
  • After compression 12.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 33.4 kB, which is 34% 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 85.2 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 75 B

  • Original 275.6 kB
  • After minification 275.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. How To Be Funny images are well optimized though.

JavaScript Optimization

-86%

Potential reduce by 98.2 kB

  • Original 114.1 kB
  • After minification 60.1 kB
  • After compression 16.0 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 98.2 kB or 86% of the original size.

CSS Optimization

-84%

Potential reduce by 7.1 kB

  • Original 8.4 kB
  • After minification 6.4 kB
  • After compression 1.3 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. How-to-be-funny.com needs all CSS files to be minified and compressed as it can save up to 7.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (62%)

Requests Now

50

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

how-to-be-funny.com accessibility score

81

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

how-to-be-funny.com best practices score

50

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

how-to-be-funny.com SEO score

67

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise How-to-be-funny.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 How-to-be-funny.com main page’s claimed encoding is iso-8859-1. 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

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