3.5 sec in total
354 ms
2.6 sec
545 ms
Visit loverofsadness.com now to see the best up-to-date Lover Of Sadness content and also check out these interesting facts you probably never knew about loverofsadness.com
Sadness... It is not something which everyone wants to be a part of. But then again there are some people like me, who are actually fascinated by it. They listen to sad songs, watch sad movies and enj...
Visit loverofsadness.comWe analyzed Loverofsadness.com page load time and found that the first response time was 354 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
loverofsadness.com performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value3.5 s
63/100
25%
Value8.3 s
19/100
10%
Value1,850 ms
9/100
30%
Value0.134
80/100
15%
Value21.3 s
1/100
10%
354 ms
11 ms
67 ms
42 ms
77 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Loverofsadness.com, 16% (21 requests) were made to Static.xx.fbcdn.net and 6% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Loverofsadness.net.
Page size can be reduced by 560.0 kB (40%)
1.4 MB
842.7 kB
In fact, the total size of Loverofsadness.com main page is 1.4 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. 80% 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 576.8 kB which makes up the majority of the site volume.
Potential reduce by 47.6 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 47.6 kB or 78% of the original size.
Potential reduce by 17.8 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. Lover Of Sadness images are well optimized though.
Potential reduce by 242.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 242.0 kB or 53% of the original size.
Potential reduce by 252.5 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. Loverofsadness.com needs all CSS files to be minified and compressed as it can save up to 252.5 kB or 82% of the original size.
Number of requests can be reduced by 55 (44%)
125
70
The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lover Of Sadness. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.loverofsadness.net
354 ms
widgets.js
11 ms
plusone.js
67 ms
jquery-ui.min.css
42 ms
LOS_all_combined.min.css--t--1390400170.gz
77 ms
jquery.min.js
61 ms
jquery-ui.min.js
100 ms
LOS_all_combined.min.js--t--1427738019.gz
200 ms
brand
30 ms
adsbygoogle.js
30 ms
show_ads.js
30 ms
brand
14 ms
cb=gapi.loaded_0
47 ms
ga.js
65 ms
all.js
94 ms
google_custom_search_watermark.gif
83 ms
12
1187 ms
ca-pub-1488509550166492.js
131 ms
zrt_lookup.html
128 ms
show_ads_impl.js
130 ms
logo.png
211 ms
Sprites.png
556 ms
body1.png
1014 ms
loading.gif
1013 ms
1734_190b1d60cdc3d01409780441e8bd3685.jpg
1014 ms
1733_6eb0057b1008a9741accff2421eb2f23.jpg
1550 ms
1726_52f79a90b9820e776e2a06bb9fe94c25.jpg
278 ms
1725_67057ecce159304847a5bfa177b2cc14.jpg
368 ms
1722_2b1fbf911fac580b050864218c4c411a.jpg
414 ms
1721_8a8dfaa86fdc2e398b5f56a8ff870945.jpg
527 ms
1707_88e973cd6b158bc7a7c5d4d407e9a29b.jpg
565 ms
1701_adba09416490ce9562922e4d3860644c.jpg
697 ms
136_dc558f57fc5d714e2288f82ee63e84a5.jpg
698 ms
135_190e27426049c7d3fadde1e2426a02a0.jpg
775 ms
134_3c4ccb5cf66276979074c896d725932d.jpg
788 ms
133_2577c3b91398dcff9671a805ec3dff37.jpg
849 ms
132_85ae29aff8106be414bffc490ce99b64.jpg
850 ms
131_b59d8fac3f22e6f9cf4e6995b9ec3e07.jpg
1013 ms
__utm.gif
70 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
150 ms
is-logged-in
1163 ms
cb=gapi.loaded_1
82 ms
fastbutton
128 ms
LQTrHj46ZQE
207 ms
likebox.php
290 ms
ads
164 ms
osd.js
102 ms
postmessageRelay
231 ms
180 ms
cb=gapi.loaded_0
73 ms
cb=gapi.loaded_1
158 ms
xd_arbiter.php
177 ms
xd_arbiter.php
334 ms
ads
295 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
180 ms
ads
253 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
91 ms
ads
255 ms
abg.js
133 ms
www-embed-player-vfl8xM8me.css
105 ms
www-embed-player.js
158 ms
base.js
262 ms
ads
213 ms
kyEKgjk51ZE.css
299 ms
kTub4bakEmM.css
343 ms
Czh0gDTFcBt.css
376 ms
N-k91nHCZS2.css
421 ms
ZeuPykSxSED.css
412 ms
q68gy-v_YMF.js
430 ms
FJmpeSpHpjS.js
452 ms
0wM5s1Khldu.js
409 ms
1bNoFZUdlYZ.js
408 ms
njO1TPvGzoR.js
446 ms
1QuX41zDRrx.js
446 ms
Oagsvfb4VWi.js
449 ms
LTv6ZK-5zxz.js
485 ms
1FCa-btixu2.js
467 ms
3193398744-postmessagerelay.js
137 ms
rpc:shindig_random.js
86 ms
jot
269 ms
3387071306135023867
53 ms
s
45 ms
m_js_controller.js
145 ms
googlelogo_color_112x36dp.png
180 ms
banner
251 ms
x_button_blue2.png
159 ms
000000_new_ico.gif
141 ms
cb=gapi.loaded_0
125 ms
banner
216 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
49 ms
ad_status.js
131 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
21 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
61 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
39 ms
VIST-Ad-Refresh_728x90_Team.jpg
97 ms
IconOnlyCollisionMarker.png
92 ms
CollisionAdMarker.png
92 ms
smds
59 ms
1609876_570939296332070_120112884_n.jpg
111 ms
safe_image.php
105 ms
safe_image.php
112 ms
safe_image.php
149 ms
562211_432972730128728_1341438081_n.jpg
111 ms
61997_1574538879527464_7196234530113012246_n.jpg
149 ms
12573204_144143442633387_9193850755063440443_n.jpg
164 ms
12801312_204554589902935_5872775999644886824_n.jpg
166 ms
12804801_191501504555084_8245397063900857033_n.jpg
167 ms
wL6VQj7Ab77.png
68 ms
s7jcwEQH7Sx.png
67 ms
QDwYpIaRyfG.png
68 ms
oxds
61 ms
I6-MnjEovm5.js
21 ms
pQrUxxo5oQp.js
35 ms
1020_345d6a3fbee4bf06c6cb7a9fdc87afb3.jpg
70 ms
948_a02243bac4c78a0feea316f19c01bca5.jpg
442 ms
255_Sad%20Eye_Jackie.jpg
67 ms
247_Tears,%20Rose%20and%20Piano_Jackie.jpg
69 ms
1016_b5c0b187fe309af0f4d35982fd961d7e.jpg
454 ms
1431_5d7943e53542ec98ced8460d6f1e51b8.jpg
128 ms
1105_97ff4fc7270266a0af059a514426a382.jpg
130 ms
328_Heart%20broken_K!M.jpg
128 ms
236_Alone%20and%20Waiting_Jackie.jpg
191 ms
162_heartbroken_jose.jpg
192 ms
1249_9ad34dc473b39537d7ee5b2ff9873b70.jpg
447 ms
56_Farewell%20my%20love!!_unknown.jpg
254 ms
ui
13 ms
xd_arbiter.php
42 ms
share_button.php
33 ms
like.php
43 ms
qeKvIRsJabD.js
70 ms
LVx-xkvaJ0b.png
18 ms
loverofsadness.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
Form elements do not have associated labels
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
loverofsadness.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
loverofsadness.com 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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Loverofsadness.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 Loverofsadness.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.
loverofsadness.com
Open Graph data is detected on the main page of Lover Of Sadness. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: