Tools & Wizards About Us
humorxl.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

humorxl.com

Humor XL ;-) The most funny videos, pictures, cartoons, jokes and more

Page Load Speed

26 sec in total

First Response

2.4 sec

Resources Loaded

23.1 sec

Page Rendered

503 ms

humorxl.com screenshot

About Website

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

Visit humorxl.com

Key Findings

We analyzed Humorxl.com page load time and found that the first response time was 2.4 sec and then it took 23.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

humorxl.com performance score

0

Network Requests Diagram

humorxl.com

2368 ms

ongein2010A.css

481 ms

vs_sitesMenu.css

223 ms

itemflv.js

229 ms

swfobject.js

48 ms

Our browser made a total of 120 requests to load all elements on the main page. We found that 23% of them (28 requests) were addressed to the original Humorxl.com, 25% (30 requests) were made to Media.ongein.nl and 7% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source .

Page Optimization Overview & Recommendations

Page size can be reduced by 659.7 kB (61%)

Content Size

1.1 MB

After Optimization

416.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Humorxl.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. 60% of websites need less resources to load. Javascripts take 801.2 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 117.2 kB

  • Original 154.7 kB
  • After minification 140.5 kB
  • After compression 37.5 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 117.2 kB or 76% of the original size.

Image Optimization

-11%

Potential reduce by 11.4 kB

  • Original 104.9 kB
  • After minification 93.5 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. Obviously, Humor XL needs image optimization as it can save up to 11.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 519.2 kB

  • Original 801.2 kB
  • After minification 689.7 kB
  • After compression 282.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 519.2 kB or 65% of the original size.

CSS Optimization

-79%

Potential reduce by 11.8 kB

  • Original 14.9 kB
  • After minification 11.7 kB
  • After compression 3.1 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. Humorxl.com needs all CSS files to be minified and compressed as it can save up to 11.8 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 55 (48%)

Requests Now

114

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

humorxl.com

humorxl.com

2368 ms

ongein2010A.css

ongein2010A.css

481 ms

vs_sitesMenu.css

vs_sitesMenu.css

223 ms

itemflv.js

itemflv.js

229 ms

swfobject.js

swfobject.js

48 ms

norclick.js

norclick.js

219 ms

admatcher.js

admatcher.js

1146 ms

shadowbox.css

shadowbox.css

221 ms

shadowbox.js

shadowbox.js

1049 ms

simpleAjax.js

simpleAjax.js

121 ms

script.leadboxer.com

script.leadboxer.com

346 ms

addthis_widget.js

addthis_widget.js

421 ms

ONGEIN.NL_24068

ONGEIN.NL_24068

299 ms

ONGEIN.NL_23502

ONGEIN.NL_23502

402 ms

ONGEIN.NL_23507

ONGEIN.NL_23507

402 ms

ONGEIN.NL_24512

ONGEIN.NL_24512

289 ms

ONGEIN.NL_24508

ONGEIN.NL_24508

290 ms

ONGEIN.NL_24507

ONGEIN.NL_24507

417 ms

ONGEIN.NL_24506

ONGEIN.NL_24506

415 ms

ONGEIN.NL_24505

ONGEIN.NL_24505

452 ms

ONGEIN.NL_24504

ONGEIN.NL_24504

414 ms

ONGEIN.NL_24502

ONGEIN.NL_24502

493 ms

ONGEIN.NL_24503

ONGEIN.NL_24503

492 ms

ONGEIN.NL_24500

ONGEIN.NL_24500

488 ms

ONGEIN.NL_24499

ONGEIN.NL_24499

490 ms

ONGEIN.NL_24501

ONGEIN.NL_24501

490 ms

ONGEIN.NL_24498

ONGEIN.NL_24498

520 ms

ONGEIN.NL_24497

ONGEIN.NL_24497

591 ms

ONGEIN.NL_24496

ONGEIN.NL_24496

586 ms

ONGEIN.NL_24495

ONGEIN.NL_24495

590 ms

ONGEIN.NL_24494

ONGEIN.NL_24494

587 ms

ONGEIN.NL_24493

ONGEIN.NL_24493

588 ms

ONGEIN.NL_24492

ONGEIN.NL_24492

613 ms

ONGEIN.NL_24491

ONGEIN.NL_24491

682 ms

ONGEIN.NL_24490

ONGEIN.NL_24490

694 ms

ONGEIN.NL_24489

ONGEIN.NL_24489

854 ms

ONGEIN.NL_24488

ONGEIN.NL_24488

849 ms

rss.png

rss.png

128 ms

EN.png

EN.png

125 ms

NL.png

NL.png

125 ms

logoen.png

logoen.png

381 ms

appStoreen.png

appStoreen.png

128 ms

homeButton.png

homeButton.png

218 ms

zoekHoekje.png

zoekHoekje.png

197 ms

zoekButton.png

zoekButton.png

184 ms

videoThumbOverlay.png

videoThumbOverlay.png

188 ms

5ster.png

5ster.png

222 ms

all.js

all.js

313 ms

topmenuleft.png

topmenuleft.png

261 ms

topmenutop.png

topmenutop.png

297 ms

topmenuright.png

topmenuright.png

298 ms

schaduwL.png

schaduwL.png

301 ms

widgets.js

widgets.js

40 ms

ONGEIN.NL_24487

ONGEIN.NL_24487

801 ms

ONGEIN.NL_24486

ONGEIN.NL_24486

802 ms

ONGEIN.NL_24485

ONGEIN.NL_24485

803 ms

schaduwR.png

schaduwR.png

294 ms

mainMenuBg.png

mainMenuBg.png

387 ms

ONGEIN.NL_24484

ONGEIN.NL_24484

795 ms

contentBg.png

contentBg.png

390 ms

serve_cad.php

serve_cad.php

617 ms

adsbygoogle.js

adsbygoogle.js

59 ms

ONGEIN.NL_2110

ONGEIN.NL_2110

987 ms

badge.gif

badge.gif

36 ms

js

js

48 ms

178 ms

xd_arbiter.php

xd_arbiter.php

238 ms

xd_arbiter.php

xd_arbiter.php

681 ms

ajax-loader.gif

ajax-loader.gif

731 ms

flowplayer.js

flowplayer.js

1078 ms

ca-pub-4982751775001804.js

ca-pub-4982751775001804.js

330 ms

zrt_lookup.html

zrt_lookup.html

537 ms

show_ads_impl.js

show_ads_impl.js

586 ms

footerBottomleft.png

footerBottomleft.png

209 ms

footerBottom.png

footerBottom.png

202 ms

footerBottomRight.png

footerBottomRight.png

203 ms

ongein.html

ongein.html

20028 ms

analytics.js

analytics.js

231 ms

ga.js

ga.js

372 ms

widget-1.4.gz.js

widget-1.4.gz.js

489 ms

log01.leadboxer.com

log01.leadboxer.com

476 ms

button.71000885400e222c3c0eec823f8f93f0.js

button.71000885400e222c3c0eec823f8f93f0.js

671 ms

ping

ping

146 ms

300lo.json

300lo.json

229 ms

plusone.js

plusone.js

230 ms

counter.270bdfcf33bafb0fc8fc.js

counter.270bdfcf33bafb0fc8fc.js

65 ms

in.php

in.php

305 ms

sh.953eb77977227bfd253ee158.html

sh.953eb77977227bfd253ee158.html

135 ms

shares.json

shares.json

149 ms

collect

collect

108 ms

login_button.php

login_button.php

161 ms

__utm.gif

__utm.gif

91 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

341 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

395 ms

fastbutton

fastbutton

475 ms

like.php

like.php

209 ms

IK_wUPJ6vpZ.js

IK_wUPJ6vpZ.js

1055 ms

teE39sffXW8.png

teE39sffXW8.png

1249 ms

iqVGY7gYXlg.gif

iqVGY7gYXlg.gif

1264 ms

Y2hhdA%3D%3D

Y2hhdA%3D%3D

314 ms

688 ms

b3BtZXJraW5nZW4%3D

b3BtZXJraW5nZW4%3D

463 ms

like.php

like.php

322 ms

ads

ads

312 ms

osd.js

osd.js

82 ms

ads

ads

319 ms

Sh_BYjerrZ8.js

Sh_BYjerrZ8.js

1401 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

1165 ms

follow_button.fd774b599f565016d763dd860cb31c79.nl.html

follow_button.fd774b599f565016d763dd860cb31c79.nl.html

56 ms

tweet_button.fd774b599f565016d763dd860cb31c79.en.html

tweet_button.fd774b599f565016d763dd860cb31c79.en.html

110 ms

info.json

info.json

312 ms

playerheight=380

playerheight=380

412 ms

postmessageRelay

postmessageRelay

231 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

105 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

147 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

187 ms

1077434459-postmessagerelay.js

1077434459-postmessagerelay.js

85 ms

rpc:shindig_random.js

rpc:shindig_random.js

41 ms

jot.html

jot.html

44 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

65 ms

SEO Factors

humorxl.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Humorxl.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 Humorxl.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

humorxl.com

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