4.7 sec in total
463 ms
4 sec
194 ms
Welcome to humor.li homepage info - get ready to check Humor best content for Germany right away, or after learning these important things about humor.li
This domain may be for sale!
Visit humor.liWe analyzed Humor.li page load time and found that the first response time was 463 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
humor.li performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value3.1 s
74/100
25%
Value3.0 s
94/100
10%
Value80 ms
99/100
30%
Value0.298
40/100
15%
Value3.2 s
94/100
10%
463 ms
309 ms
564 ms
219 ms
7 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 29% of them (21 requests) were addressed to the original Humor.li, 11% (8 requests) were made to Pic.humor.li and 10% (7 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (574 ms) belongs to the original domain Humor.li.
Page size can be reduced by 83.8 kB (21%)
402.3 kB
318.5 kB
In fact, the total size of Humor.li main page is 402.3 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. 45% of websites need less resources to load. Images take 211.2 kB which makes up the majority of the site volume.
Potential reduce by 44.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 44.5 kB or 78% of the original size.
Potential reduce by 4.0 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. Humor images are well optimized though.
Potential reduce by 35.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 35.4 kB or 26% of the original size.
Number of requests can be reduced by 36 (55%)
65
29
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Humor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.
humor.li
463 ms
css
309 ms
js
564 ms
fo.js
219 ms
fo.js
7 ms
ga.js
44 ms
tile.jpg
118 ms
headerbg.png
205 ms
logo.png
210 ms
footerbg.png
213 ms
facebook_32.png
231 ms
email_32.png
224 ms
all.js
6 ms
ui-bg_flat_75_ffffff_40x100.png
297 ms
116 ms
__utm.gif
30 ms
xd_arbiter.php
24 ms
xd_arbiter.php
30 ms
fmr.js
118 ms
yield.js
280 ms
trk.js
277 ms
adsbygoogle.js
9 ms
track.php
541 ms
ca-pub-0089357498707646.js
28 ms
zrt_lookup.html
18 ms
show_ads_impl.js
59 ms
fo.js
9 ms
fm.js
145 ms
ads
353 ms
osd.js
4 ms
yield.js
252 ms
trk.js
3 ms
ads
192 ms
fm.js
132 ms
track.php
494 ms
m_js_controller.js
18 ms
abg.js
27 ms
googlelogo_color_112x36dp.png
48 ms
nessie_icon_tiamat_white.png
20 ms
s
11 ms
x_button_blue2.png
3 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
2 ms
yield.js
271 ms
11243099795855977832
16 ms
imp
8 ms
flash_embed4.js
21 ms
D_affiliate_juli_2013_sujet1_300x250.jpg
418 ms
activeview
56 ms
ui-icons_222222_256x240.png
129 ms
RandomJoke
332 ms
NewMovies
292 ms
NewPictures
324 ms
NewPowerpoints
318 ms
ads
186 ms
xd_arbiter.php
4 ms
getmovieprev.aspx
530 ms
getmovieprev.aspx
528 ms
getmovieprev.aspx
551 ms
getmovieprev.aspx
574 ms
star-full.png
126 ms
star-empty.png
118 ms
getfunfilesprev.aspx
330 ms
getfunfilesprev.aspx
334 ms
humor-li-thumb-139645.jpg
302 ms
humor-li-thumb-140594.jpg
302 ms
humor-li-thumb-137116.jpg
300 ms
humor-li-thumb-130145.jpg
301 ms
activeview
17 ms
humor-li-movie-11136.jpg
98 ms
humor-li-movie-11141.jpg
98 ms
humor-li-movie-11139.jpg
98 ms
humor-li-movie-11143.jpg
98 ms
humor.li accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
humor.li best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Uses deprecated APIs
humor.li SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Humor.li can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Humor.li 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.
humor.li
Open Graph description is not detected on the main page of Humor. 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: