5 sec in total
326 ms
3.1 sec
1.6 sec
Click here to check amazing Headunderwater content. Otherwise, check out these important facts you probably never knew about headunderwater.com
Tumblr. Pure effervescent enrichment. Old internet energy. Home of the Reblogs. All the art you never knew you needed. All the fandoms you could wish for. Enough memes to knock out a moderately-sized ...
Visit headunderwater.comWe analyzed Headunderwater.com page load time and found that the first response time was 326 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
headunderwater.com performance score
name
value
score
weighting
Value2.4 s
69/100
10%
Value4.2 s
43/100
25%
Value3.5 s
89/100
10%
Value230 ms
87/100
30%
Value0.012
100/100
15%
Value5.4 s
71/100
10%
326 ms
25 ms
34 ms
181 ms
16 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Headunderwater.com, 18% (20 requests) were made to Jimmy-morris.com and 11% (12 requests) were made to W.soundcloud.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Jimmy-morris.com.
Page size can be reduced by 1.4 MB (32%)
4.4 MB
3.0 MB
In fact, the total size of Headunderwater.com main page is 4.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. 85% 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 2.3 MB which makes up the majority of the site volume.
Potential reduce by 90.2 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. This page needs HTML code to be minified as it can gain 24.5 kB, which is 23% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 90.2 kB or 84% of the original size.
Potential reduce by 12.1 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. Headunderwater images are well optimized though.
Potential reduce by 842.1 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 842.1 kB or 68% of the original size.
Potential reduce by 465.8 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. Headunderwater.com needs all CSS files to be minified and compressed as it can save up to 465.8 kB or 63% of the original size.
Number of requests can be reduced by 48 (46%)
104
56
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Headunderwater. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.headunderwater.com
326 ms
pre_tumblelog.js
25 ms
css
34 ms
styles.css
181 ms
jquery.min.js
16 ms
modernizr.js
207 ms
swag-makers.js
235 ms
widgets.js
95 ms
tumblelog_post_message_queue.js
21 ms
stylesheet.css
25 ms
index.js
21 ms
normalize.min.css
82 ms
wood.jpg
172 ms
ga.js
67 ms
all.js
73 ms
113884040
236 ms
525 ms
496 ms
tumblr_inline_nkeak3X34H1qz9ffq.jpg
190 ms
509 ms
496 ms
tumblr_inline_njvr20xLVl1qz9ffq.jpg
202 ms
493 ms
491 ms
9qPV0dvy4cQ
482 ms
530 ms
n78GkK7LC9Y
557 ms
real-estate.jpg
347 ms
logo.png
331 ms
mag-glass.gif
331 ms
sprite.png
331 ms
estivated.jpg
718 ms
recrudesce.jpg
520 ms
whitehurstfrwy.jpg
464 ms
no-rush.jpg
463 ms
BEARHAUS.jpg
1260 ms
kibbles.jpg
871 ms
fuw-thumb.jpg
584 ms
topeka-thumb.jpg
718 ms
piedmont-thumb.jpg
743 ms
arlington-thumb.jpg
759 ms
tumblr_inline_njmq2vjGuC1qz9ffq.jpg
462 ms
tumblr_inline_nk11c2DnBJ1qz9ffq.jpg
145 ms
tumblr_inline_njb4lrBRB31qz9ffq.jpg
143 ms
__utm.gif
218 ms
player.js
470 ms
player.css
449 ms
ga.js
396 ms
vuid.min.js
448 ms
B0txb0blf2N29WdYPJjMShZ1gqmQBTb4Nwa_fF0DajA.woff
307 ms
Ez4zJbsGr2BgXcNUWBVgEFxo_3fQgeDvKMambfIp_uA.woff
325 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
355 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
360 ms
xjAJXh38I15wypJXxuGMBobN6UDyHWBl620a-IRfuBk.woff
359 ms
PRmiXeptR36kaC0GEAetxjqR_3kx9_hJXbbyU8S6IN0.woff
354 ms
586 ms
xd_arbiter.php
292 ms
xd_arbiter.php
429 ms
impixu
409 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
477 ms
analytics.html
394 ms
dirtybeaches.jpg
684 ms
impixu
393 ms
login_check.html
47 ms
interstate-0ab59479718c8235122cad6b16a66953d725c43a.css
844 ms
widget-0511d506.css
262 ms
widget-d9304090.js
310 ms
avatar_120a6f1b9365_40.png
97 ms
iframe_logo.png
301 ms
www-embed-player-vflfNyN_r.css
301 ms
www-embed-player.js
352 ms
base.js
577 ms
like.php
350 ms
__utm.gif
151 ms
rapid-3.36.js
350 ms
rapidworker-1.2.js
368 ms
proxy.html
168 ms
500213556.webp
508 ms
like.php
155 ms
like.php
515 ms
like.php
512 ms
like.php
512 ms
like.php
508 ms
like.php
508 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
168 ms
like.php
377 ms
like.php
734 ms
like.php
731 ms
qeKvIRsJabD.js
499 ms
LVx-xkvaJ0b.png
717 ms
qeKvIRsJabD.js
969 ms
analytics.js
401 ms
xd_arbiter.php
189 ms
cs.js
868 ms
__utm.gif
361 ms
yql
1084 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
707 ms
ad_status.js
706 ms
qeKvIRsJabD.js
663 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
645 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
735 ms
qeKvIRsJabD.js
606 ms
logo-200x120-177df3dd.png
475 ms
visual-single-sound-cd67be80.js
364 ms
error-698b3c1d.js
359 ms
qeKvIRsJabD.js
368 ms
qeKvIRsJabD.js
262 ms
__utm.gif
186 ms
__utm.gif
166 ms
__utm.gif
259 ms
__utm.gif
258 ms
__utm.gif
259 ms
jot.html
63 ms
headunderwater.com 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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.
headunderwater.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
headunderwater.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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Headunderwater.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 Headunderwater.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.
headunderwater.com
Open Graph description is not detected on the main page of Headunderwater. 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: