Tools & Wizards About Us
funnieststuff.net screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

funnieststuff.net

Page Load Speed

1.8 sec in total

First Response

141 ms

Resources Loaded

1.4 sec

Page Rendered

228 ms

funnieststuff.net screenshot

About Website

Welcome to funnieststuff.net homepage info - get ready to check Funnieststuff best content for United States right away, or after learning these important things about funnieststuff.net

Funny viral stuff

Visit funnieststuff.net

Key Findings

We analyzed Funnieststuff.net page load time and found that the first response time was 141 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

funnieststuff.net performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value1,520 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value5.0 s

76/100

10%

Network Requests Diagram

funnieststuff.net

141 ms

browseissues.php

66 ms

screen.css

59 ms

show_ads.js

8 ms

typography.css

57 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Funnieststuff.net, 26% (7 requests) were made to Blog.funnieststuff.net and 15% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (508 ms) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

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

Content Size

76.2 kB

After Optimization

47.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Funnieststuff.net main page is 76.2 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. 55% of websites need less resources to load. HTML takes 21.5 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 16.2 kB

  • Original 21.5 kB
  • After minification 20.0 kB
  • After compression 5.3 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 16.2 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 21.3 kB
  • After minification 21.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. Funnieststuff images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 172 B

  • Original 17.5 kB
  • After minification 17.4 kB
  • After compression 17.3 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

-79%

Potential reduce by 12.5 kB

  • Original 15.9 kB
  • After minification 12.8 kB
  • After compression 3.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. Funnieststuff.net needs all CSS files to be minified and compressed as it can save up to 12.5 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (42%)

Requests Now

24

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

funnieststuff.net

funnieststuff.net

141 ms

browseissues.php

browseissues.php

66 ms

screen.css

screen.css

59 ms

show_ads.js

show_ads.js

8 ms

typography.css

typography.css

57 ms

layout.css

layout.css

60 ms

color.css

color.css

58 ms

sdk.js

sdk.js

83 ms

buttons.js

buttons.js

391 ms

ca-pub-7089968998080950.js

ca-pub-7089968998080950.js

475 ms

zrt_lookup.html

zrt_lookup.html

508 ms

show_ads_impl.js

show_ads_impl.js

142 ms

ga.js

ga.js

271 ms

header_background.jpg

header_background.jpg

315 ms

logo.png

logo.png

314 ms

ads

ads

380 ms

343 ms

osd.js

osd.js

200 ms

__utm.gif

__utm.gif

150 ms

xd_arbiter.php

xd_arbiter.php

203 ms

xd_arbiter.php

xd_arbiter.php

237 ms

ads

ads

185 ms

like.php

like.php

133 ms

share_button.php

share_button.php

143 ms

fy8tT2klpgR.js

fy8tT2klpgR.js

99 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

77 ms

fy8tT2klpgR.js

fy8tT2klpgR.js

48 ms

Accessibility Review

funnieststuff.net accessibility score

60

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

Document doesn't have a <title> element

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

funnieststuff.net best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

funnieststuff.net 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

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • 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 Funnieststuff.net 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Funnieststuff.net 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

funnieststuff.net

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