1.4 sec in total
200 ms
959 ms
254 ms
Visit lolme.org now to see the best up-to-date Lolme content and also check out these interesting facts you probably never knew about lolme.org
LOL me - funny lol pics, game and videos
Visit lolme.orgWe analyzed Lolme.org page load time and found that the first response time was 200 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
lolme.org performance score
name
value
score
weighting
Value0.8 s
100/100
10%
Value0.8 s
100/100
25%
Value0.8 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.8 s
100/100
10%
200 ms
152 ms
10 ms
20 ms
19 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 11% of them (6 requests) were addressed to the original Lolme.org, 35% (20 requests) were made to Pics.lolme.org and 26% (15 requests) were made to 1.gravatar.com. The less responsive or slowest element that took the longest time to load (200 ms) belongs to the original domain Lolme.org.
Page size can be reduced by 294.5 kB (50%)
594.8 kB
300.4 kB
In fact, the total size of Lolme.org main page is 594.8 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. 50% of websites need less resources to load. Javascripts take 220.4 kB which makes up the majority of the site volume.
Potential reduce by 37.4 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 37.4 kB or 81% of the original size.
Potential reduce by 7.4 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. Lolme images are well optimized though.
Potential reduce by 135.6 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 135.6 kB or 62% of the original size.
Potential reduce by 114.2 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. Lolme.org needs all CSS files to be minified and compressed as it can save up to 114.2 kB or 83% of the original size.
Number of requests can be reduced by 5 (9%)
55
50
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lolme. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
www.lolme.org
200 ms
cloudflare.min.js
152 ms
default.include.ce2b54.css
10 ms
jquery.min.js
20 ms
default.include-body.e119d5.js
19 ms
ga.js
123 ms
logo.jpg
115 ms
cat-snowmobile-ride-230x230.gif
111 ms
8871a9e85069d38bbfca7c35079ffefe
113 ms
f49ea3063bf4a34f4e759934d9e74419
110 ms
gpt.js
54 ms
ajax-loader.gif
54 ms
does-apple-ipad-air-2-bend-yes-i-230x129.jpg
44 ms
square-bubble-230x149.gif
45 ms
what-happen-after-sex-230x228.jpg
187 ms
the-most-epic-basketball-shot-ev-230x129.jpg
47 ms
sickest-prank-giant-mutant-spider-230x128.jpg
48 ms
rescuing-stucked-prairie-dog-in-230x408.jpg
45 ms
samsung-galaxy-s5-takes-alc-ice-230x129.jpg
42 ms
instagram-gold-digger-prank-230x128.jpg
45 ms
funny-cat-vines-230x129.jpg
48 ms
als-ice-bucket-challenge-fail-co-230x172.jpg
53 ms
als-ice-bucket-challenge-fail-230x409.jpg
49 ms
motorcycle-crash-ends-in-the-cra-230x172.jpg
52 ms
balkan-floods-short-animated-mov-230x129.jpg
50 ms
morgan-freeman-on-helium-230x129.jpg
50 ms
man-scared-while-wearing-oculus-230x129.jpg
52 ms
shoe-thrown-at-hillary-clinton-230x172.jpg
53 ms
fake-pregnancy-april-fools-prank-230x129.jpg
54 ms
dutch-reporter-dives-into-worst-230x129.jpg
54 ms
this-is-how-the-cops-are-stoppin-230x172.jpg
55 ms
862e9a2860407db176fca5db24c98571
95 ms
a1b350449555b06abd0baed0011ae5b8
99 ms
6eb7dc170323b24bedd4103ed9ec0948
103 ms
c2b968304c7c86e69ecaa3e1700d807e
102 ms
40a9534e22a0c847559a63b06bfaa909
105 ms
cf72973eaa07f033e76ea160b7a5c4c7
100 ms
64a9ab8fbbad9885d8a4d7f9035049d4
105 ms
07b90eb0859047884a2c97e1381a84fe
112 ms
b86022581860aaaa5a865bdb7cc52439
92 ms
d9c82c762dfdd324e0b3dbdb8b1deacf
100 ms
f4e4f129dfe01eccdf80d2c6aed167b2
105 ms
7c2dd43702cfdf5c500a4b9ad719a029
105 ms
5501dd85b7626f3fb490e83ad1fd970d
105 ms
d4d2ba65837195a05586e15f15aa0bcb
107 ms
7eb4d8fad71ad8d6471a812ac1034855
107 ms
b8f33f7bd6e4829daca939e4f18bd042
108 ms
39260c37cd6dd77ba242934b1c2294ab
110 ms
7530bcca34f769e9437559f94f680199
108 ms
f49ea3063bf4a34f4e759934d9e74419
110 ms
1ebcf3f90a9542ddfa3ed867833b9e97
110 ms
34b7c0cf0c4c4d1162e6aecbb32ea91d
115 ms
b366ffb6b4f384c1c7ff496549ef4922
118 ms
fontawesome-webfont.woff
192 ms
__utm.gif
40 ms
pubads_impl_82.js
35 ms
container.html
35 ms
lolme.org accessibility score
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
Document doesn't have a <title> element
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
lolme.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
lolme.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lolme.org 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), while the claimed language is English. Our system also found out that Lolme.org 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.
lolme.org
Open Graph data is detected on the main page of Lolme. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: