5.3 sec in total
449 ms
2.3 sec
2.6 sec
Click here to check amazing Cannot Unsee content for United States. Otherwise, check out these important facts you probably never knew about cannotunsee.net
Have you ever noticed that once you see something in a certain light, you always imagine it that way afterwards? Cannot Unsee is a place that unwraps your childhood heroes and dreams and turns them...
Visit cannotunsee.netWe analyzed Cannotunsee.net page load time and found that the first response time was 449 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
cannotunsee.net performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value9.5 s
0/100
25%
Value5.8 s
50/100
10%
Value2,550 ms
4/100
30%
Value0
100/100
15%
Value18.5 s
3/100
10%
449 ms
18 ms
30 ms
28 ms
31 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 10% of them (12 requests) were addressed to the original Cannotunsee.net, 18% (23 requests) were made to Static.tumblr.com and 11% (14 requests) were made to 40.media.tumblr.com. The less responsive or slowest element that took the longest time to load (565 ms) relates to the external source 40.media.tumblr.com.
Page size can be reduced by 1.6 MB (32%)
5.1 MB
3.5 MB
In fact, the total size of Cannotunsee.net main page is 5.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. 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 3.1 MB which makes up the majority of the site volume.
Potential reduce by 135.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 135.8 kB or 81% of the original size.
Potential reduce by 189.9 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. Cannot Unsee images are well optimized though.
Potential reduce by 975.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 975.0 kB or 65% of the original size.
Potential reduce by 334.7 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. Cannotunsee.net needs all CSS files to be minified and compressed as it can save up to 334.7 kB or 85% of the original size.
Number of requests can be reduced by 60 (54%)
112
52
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cannot Unsee. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.cannotunsee.net
449 ms
pre_tumblelog.js
18 ms
reset.css
30 ms
skeleton.css
28 ms
yummi-loader.css
31 ms
owl.carousel.css
25 ms
smartmenus.css
29 ms
colorbox.css
29 ms
css
38 ms
jquery.min.1.8.2.js
35 ms
tumblelog_post_message_queue.js
22 ms
stylesheet.css
26 ms
adsbygoogle.js
26 ms
show_ads.js
29 ms
jquery.smartmenus.js
25 ms
jquery.nicescroll.min.js
28 ms
jquery.fitvids.js
24 ms
jquery.photoset-grid.js
24 ms
jquery.colorbox.js
25 ms
scroll-to-top.js
27 ms
yummi-loader.js
27 ms
owl.carousel.js
76 ms
tumblr-rss.js
27 ms
jquery.share.js
27 ms
index.js
22 ms
avatar_0f79c13d1bc2_96.png
278 ms
tumblr_o41bvueu7J1qbn1vmo1_500.jpg
281 ms
tumblr_o3u0wlnK2t1qfec9so2_500.jpg
112 ms
tumblr_o3u0wlnK2t1qfec9so1_500.jpg
111 ms
IvUU8joBb1Q
158 ms
AqCZTfonTNw
304 ms
count.js
136 ms
zrt_lookup.html
148 ms
show_ads_impl.js
150 ms
tumblr_o372e6yXPW1qbn1vmo1_r1_1280.jpg
565 ms
tumblr_static_1kyr0vmllyv44sg8wocwwsokw.jpg
332 ms
476.gif
105 ms
tumblr_static_2l9b03288oyswg4g44w8cw4kg.png
282 ms
sprite.png
104 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
105 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
115 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
130 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
129 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
129 ms
ca-pub-9923789228994794.js
49 ms
PRmiXeptR36kaC0GEAetxjqR_3kx9_hJXbbyU8S6IN0.woff
47 ms
PRmiXeptR36kaC0GEAetxkCDe67GEgBv_HnyvHTfdew.woff
46 ms
PRmiXeptR36kaC0GEAetxn5HxGBcBvicCpTp6spHfNo.woff
46 ms
xjAJXh38I15wypJXxuGMBobN6UDyHWBl620a-IRfuBk.woff
61 ms
PRmiXeptR36kaC0GEAetxh_xHqYgAV9Bl_ZQbYUxnQU.woff
60 ms
count-data.js
217 ms
www-embed-player-vflfNyN_r.css
177 ms
www-embed-player.js
202 ms
ads
402 ms
ads
385 ms
cd-top-arrow.svg
34 ms
osd.js
81 ms
ga.js
257 ms
tumblr_o3u0wlnK2t1qfec9so2_1280.jpg
498 ms
tumblr_o3u0wlnK2t1qfec9so1_1280.jpg
446 ms
impixu
351 ms
IvUU8joBb1Q
136 ms
impixu
231 ms
AqCZTfonTNw
194 ms
analytics.html
187 ms
login_check.html
66 ms
__utm.gif
67 ms
banner
208 ms
banner
194 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
127 ms
ad_status.js
132 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
122 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
221 ms
json
199 ms
json
199 ms
json
274 ms
json
243 ms
json
317 ms
json
274 ms
rapid-3.36.js
160 ms
rapidworker-1.2.js
165 ms
json
250 ms
json
237 ms
json
306 ms
json
397 ms
json
304 ms
VIST-Ad-Refresh_160x600_Coaching.jpg
248 ms
IconOnlyCollisionMarker.png
175 ms
CollisionAdMarker.png
175 ms
VIST-Ad-Refresh_300x600_Potential.jpg
208 ms
ga.js
152 ms
analytics.js
150 ms
tumblr_o11jlth1Mu1qbn1vmo1_400.jpg
75 ms
tumblr_nv5n8slgpt1qbn1vmo1_400.jpg
76 ms
date_icon.png
74 ms
tumblr_nvdefqcTiB1qbn1vmo1_400.jpg
68 ms
cs.js
198 ms
yql
336 ms
smds
169 ms
tumblr_o1e3wcx73q1rjjqhuo1_400.jpg
126 ms
tumblr_nx1lxeK9ci1qbn1vmo1_400.jpg
124 ms
tumblr_nri64ntGtE1qbn1vmo1_400.jpg
65 ms
tumblr_ntyjpaYfkL1qbn1vmo3_400.jpg
52 ms
tumblr_nk7da0oRyu1qbn1vmo1_400.gif
329 ms
tumblr_nkezkhKlIT1qbn1vmo2_400.jpg
174 ms
tumblr_n4r8ifACFC1qbn1vmo1_400.jpg
173 ms
tumblr_n8f6i82Nvj1qbn1vmo1_400.jpg
320 ms
tumblr_n28em7GDSr1qbn1vmo4_400.jpg
44 ms
tumblr_n00ug2mAev1t0qklto1_400.png
417 ms
tumblr_n3omxfN7X91qcm16uo1_400.jpg
42 ms
tumblr_mthw9vk2gV1qb5gkjo2_400.jpg
76 ms
tumblr_o1ml05GC6a1qbn1vmo6_400.jpg
44 ms
tumblr_nxmgphBokf1qbn1vmo1_400.jpg
77 ms
oxds
161 ms
__utm.gif
51 ms
tumblr_o41bvueu7J1qbn1vmo1_400.jpg
77 ms
1kt3OVwGPtM
142 ms
139407849
163 ms
tumblr_nl0w1ixEMN1qbn1vmo1_400.jpg
94 ms
WxK_WJ-V1c8
175 ms
IdlZRhKmWJY
162 ms
player.js
196 ms
player.css
196 ms
vuid.min.js
209 ms
__utm.gif
55 ms
cannotunsee.net 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
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
cannotunsee.net 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
cannotunsee.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cannotunsee.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Cannotunsee.net 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.
cannotunsee.net
Open Graph data is detected on the main page of Cannot Unsee. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: