Tools & Wizards About Us
humorlulz.com screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

humorlulz.com

Home - CDR LLC

Page Load Speed

3.2 sec in total

First Response

14 ms

Resources Loaded

2.4 sec

Page Rendered

749 ms

humorlulz.com screenshot

About Website

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

Visit humorlulz.com

Key Findings

We analyzed Humorlulz.com page load time and found that the first response time was 14 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

humorlulz.com performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value540 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.147

77/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

humorlulz.com

14 ms

cdrllctx.com

1279 ms

style.min.css

249 ms

styles.css

187 ms

nectar-slider.css

192 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Humorlulz.com, 82% (69 requests) were made to Cdrllctx.com and 8% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Cdrllctx.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 212.6 kB (12%)

Content Size

1.8 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Humorlulz.com main page is 1.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 94.1 kB

  • Original 111.8 kB
  • After minification 108.7 kB
  • After compression 17.7 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 94.1 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 25.8 kB

  • Original 1.1 MB
  • After minification 1.0 MB

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. Humorlulz images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 57.7 kB

  • Original 504.1 kB
  • After minification 504.1 kB
  • After compression 446.4 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 57.7 kB or 11% of the original size.

CSS Optimization

-21%

Potential reduce by 35.0 kB

  • Original 165.1 kB
  • After minification 164.9 kB
  • After compression 130.0 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. Humorlulz.com needs all CSS files to be minified and compressed as it can save up to 35.0 kB or 21% of the original size.

Requests Breakdown

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

Requests Now

73

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

humorlulz.com

humorlulz.com

14 ms

cdrllctx.com

cdrllctx.com

1279 ms

style.min.css

style.min.css

249 ms

styles.css

styles.css

187 ms

nectar-slider.css

nectar-slider.css

192 ms

font-awesome-legacy.min.css

font-awesome-legacy.min.css

189 ms

grid-system.css

grid-system.css

187 ms

style.css

style.css

300 ms

header-secondary-nav.css

header-secondary-nav.css

251 ms

cf7.css

cf7.css

252 ms

css

css

38 ms

responsive.css

responsive.css

252 ms

flickity.css

flickity.css

254 ms

select2.css

select2.css

309 ms

skin-material.css

skin-material.css

310 ms

menu-dynamic.css

menu-dynamic.css

313 ms

js_composer.min.css

js_composer.min.css

312 ms

salient-dynamic-styles.css

salient-dynamic-styles.css

371 ms

style.css

style.css

356 ms

css

css

33 ms

jquery.min.js

jquery.min.js

426 ms

jquery-migrate.min.js

jquery-migrate.min.js

378 ms

api.js

api.js

39 ms

js

js

84 ms

style-non-critical.css

style-non-critical.css

219 ms

jquery.fancybox.css

jquery.fancybox.css

219 ms

core.css

core.css

260 ms

slide-out-right-hover.css

slide-out-right-hover.css

340 ms

index.js

index.js

340 ms

index.js

index.js

340 ms

anime.min.js

anime.min.js

341 ms

nectar-slider.js

nectar-slider.js

393 ms

jquery.easing.min.js

jquery.easing.min.js

393 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

392 ms

priority.js

priority.js

392 ms

nectar-slider-priority.js

nectar-slider-priority.js

393 ms

transit.min.js

transit.min.js

391 ms

waypoints.js

waypoints.js

463 ms

imagesLoaded.min.js

imagesLoaded.min.js

464 ms

hoverintent.min.js

hoverintent.min.js

464 ms

jquery.fancybox.js

jquery.fancybox.js

464 ms

flickity.js

flickity.js

464 ms

superfish.js

superfish.js

453 ms

init.js

init.js

531 ms

touchswipe.min.js

touchswipe.min.js

449 ms

select2.min.js

select2.min.js

501 ms

js_composer_front.min.js

js_composer_front.min.js

446 ms

cdr-logo.svg

cdr-logo.svg

195 ms

cdr-logo.png

cdr-logo.png

195 ms

aatc.png

aatc.png

268 ms

aagd.png

aagd.png

268 ms

bbb.png

bbb.png

313 ms

fwqueensgarden-img-1.jpg

fwqueensgarden-img-1.jpg

313 ms

fwqueensgarden-img-2.jpg

fwqueensgarden-img-2.jpg

366 ms

fwqueensgarden-img-3.jpg

fwqueensgarden-img-3.jpg

431 ms

fwqueensgarden-img-4.jpg

fwqueensgarden-img-4.jpg

427 ms

fwqueensgarden-img-5.jpg

fwqueensgarden-img-5.jpg

428 ms

fwqueensgarden-img-6.jpg

fwqueensgarden-img-6.jpg

402 ms

fwqueensgarden-img-7.jpg

fwqueensgarden-img-7.jpg

401 ms

fwqueensgarden-img-8.jpg

fwqueensgarden-img-8.jpg

404 ms

fwqueensgarden-img-9.jpg

fwqueensgarden-img-9.jpg

443 ms

fwqueensgarden-img-10.jpg

fwqueensgarden-img-10.jpg

445 ms

recaptcha__en.js

recaptcha__en.js

120 ms

embed

embed

193 ms

fwqueensgarden-img-11.jpg

fwqueensgarden-img-11.jpg

409 ms

fwqueensgarden-img-12.jpg

fwqueensgarden-img-12.jpg

435 ms

fwqueensgarden-img-13.jpg

fwqueensgarden-img-13.jpg

436 ms

fwqueensgarden-img-14.jpg

fwqueensgarden-img-14.jpg

436 ms

test-1.png

test-1.png

388 ms

test-2.png

test-2.png

388 ms

images.png

images.png

409 ms

cdr-logo-white.svg

cdr-logo-white.svg

437 ms

home-about.jpg

home-about.jpg

622 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

71 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYA.ttf

122 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

169 ms

icomoon.woff

icomoon.woff

362 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

496 ms

js

js

155 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

89 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

118 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

117 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

117 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

126 ms

Accessibility Review

humorlulz.com accessibility score

82

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

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

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

humorlulz.com best practices score

92

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

SEO Factors

humorlulz.com SEO score

93

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

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 Humorlulz.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 Humorlulz.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

humorlulz.com

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