2.4 sec in total
255 ms
1.7 sec
476 ms
Welcome to ugly.life homepage info - get ready to check Ugly best content for United States right away, or after learning these important things about ugly.life
hi i'm ugly and i'm probably hungry
Visit ugly.lifeWe analyzed Ugly.life page load time and found that the first response time was 255 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
ugly.life performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value3.8 s
56/100
25%
Value4.9 s
65/100
10%
Value820 ms
36/100
30%
Value0.029
100/100
15%
Value9.3 s
32/100
10%
255 ms
19 ms
25 ms
41 ms
59 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Ugly.life, 14% (8 requests) were made to Static.tumblr.com and 14% (8 requests) were made to Assets.tumblr.com. The less responsive or slowest element that took the longest time to load (597 ms) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 415.2 kB (26%)
1.6 MB
1.2 MB
In fact, the total size of Ugly.life main page is 1.6 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. 65% of websites need less resources to load. Images take 987.3 kB which makes up the majority of the site volume.
Potential reduce by 36.8 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 36.8 kB or 73% of the original size.
Potential reduce by 47.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. Ugly images are well optimized though.
Potential reduce by 330.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 330.0 kB or 57% of the original size.
Potential reduce by 1.3 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. Ugly.life needs all CSS files to be minified and compressed as it can save up to 1.3 kB or 88% of the original size.
Number of requests can be reduced by 25 (45%)
55
30
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ugly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
ugly.life
255 ms
pre_tumblelog.js
19 ms
tumblelog_post_message_queue.js
25 ms
stylesheet.css
41 ms
counter.php
59 ms
adsbygoogle.js
7 ms
index.js
38 ms
tumblr_inline_nfixl72X9x1saa4gh.gif
107 ms
candy_crush.png
110 ms
icon.png
76 ms
retro_mario_world.png
92 ms
billiards-icon.png
115 ms
tumblr_static_1uw8be3qb0sg4ck4c4k4w88g4.png
78 ms
tumblr_inline_nfixyf72Hj1saa4gh.gif
108 ms
tumblr_inline_nfixppTQZK1saa4gh.png
109 ms
tumblr_inline_nfixrixkkE1saa4gh.png
124 ms
tumblr_inline_nfixnfPvUP1saa4gh.gif
108 ms
sdk.js
356 ms
ocounter.php
217 ms
tumblr_o186gcEuTd1umeg0go1_500.jpg
51 ms
tumblr_ny96r87wqD1umeg0go1_500.jpg
175 ms
tumblr_static_ab8fuod2n2wc8wckk0c8ck8kw.jpg
109 ms
tumblr_static_tumblr_static_adxihijbyagc0448os4k4cc0g_focused_v3.gif
150 ms
tumblr_static_f0i4pyrflzc4ks0okg0g408cw.png
78 ms
tumblr_o18aaxoBcx1umeg0go1_500.jpg
65 ms
ca-pub-8126130842767723.js
217 ms
zrt_lookup.html
253 ms
show_ads_impl.js
140 ms
impixu
285 ms
impixu
216 ms
analytics.html
205 ms
login_check.html
154 ms
counter.js
159 ms
ads
248 ms
209 ms
t.php
83 ms
osd.js
39 ms
xd_arbiter.php
257 ms
xd_arbiter.php
510 ms
rapid-3.33.js
39 ms
rapidworker-1.2.js
35 ms
ga.js
118 ms
analytics.js
94 ms
cs.js
84 ms
yql
244 ms
like.php
111 ms
m_js_controller.js
69 ms
abg.js
85 ms
__utm.gif
30 ms
rU2ubZ6l1Q5.js
536 ms
LVx-xkvaJ0b.png
597 ms
favicon
107 ms
googlelogo_color_112x36dp.png
102 ms
nessie_icon_tiamat_white.png
34 ms
s
19 ms
x_button_blue2.png
12 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
9 ms
cedexis.radar.js
3 ms
ui
50 ms
ugly.life 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
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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
Links do not have a discernible name
ugly.life best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
ugly.life SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ugly.life 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 Ugly.life 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.
ugly.life
Open Graph data is detected on the main page of Ugly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: