2.9 sec in total
354 ms
2 sec
611 ms
Click here to check amazing Humm content for United States. Otherwise, check out these important facts you probably never knew about humm.ly
Humm.ly music wellness app combining music therapy & mindfulness techniques for your health. Learn how your life can improve in a click.
Visit humm.lyWe analyzed Humm.ly page load time and found that the first response time was 354 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
humm.ly performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value8.4 s
2/100
25%
Value4.9 s
65/100
10%
Value930 ms
30/100
30%
Value0.039
100/100
15%
Value10.2 s
25/100
10%
354 ms
75 ms
123 ms
85 ms
108 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 73% of them (58 requests) were addressed to the original Humm.ly, 6% (5 requests) were made to Connect.facebook.net and 5% (4 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (842 ms) belongs to the original domain Humm.ly.
Page size can be reduced by 35.7 kB (23%)
152.7 kB
117.1 kB
In fact, the total size of Humm.ly main page is 152.7 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. 65% of websites need less resources to load. CSS take 65.0 kB which makes up the majority of the site volume.
Potential reduce by 28.5 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 28.5 kB or 73% of the original size.
Potential reduce by 5.5 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. Obviously, Humm needs image optimization as it can save up to 5.5 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.4 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. This website has mostly compressed JavaScripts.
Potential reduce by 293 B
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. Humm.ly has all CSS files already compressed.
Number of requests can be reduced by 44 (58%)
76
32
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Humm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
humm.ly
354 ms
www.humm.ly
75 ms
gtm.js
123 ms
style.css
85 ms
material-design-iconic-font.min.css
108 ms
custom-animate.css
160 ms
ripple.min.css
259 ms
venobox.css
112 ms
slick.min.css
158 ms
responsive.css
122 ms
newstyle.css
197 ms
aos.css
104 ms
bootstrap.min.css
166 ms
all.css
258 ms
subscribe.css
163 ms
blog.css
262 ms
modernizr-2.8.3.min.js
261 ms
fontawesome.js
298 ms
word-wall.css
306 ms
promotion_landing.css
301 ms
promotion_landing2.css
316 ms
index.css
316 ms
jquery-3.3.1.slim.min.js
79 ms
popper.min.js
95 ms
bootstrap.min.js
85 ms
imagesloaded.pkgd.min.js
293 ms
jquery.cookie.js
102 ms
jquery.validate.min.js
303 ms
validate-active.js
432 ms
slick.min.js
345 ms
vue.min.js
84 ms
aos.min.js
434 ms
nav.js
377 ms
utilities.js
354 ms
index.js
422 ms
defer.js
436 ms
v652eace1692a40cfa3763df669d7439c1639079717194
120 ms
fbevents.js
25 ms
js
45 ms
identity.js
63 ms
4101024303321277
127 ms
491a82ae7c.css
193 ms
style.css
47 ms
font-awesome-css.min.css
44 ms
css
186 ms
css
187 ms
sdk.js
143 ms
logo.webp
218 ms
en_badge_web_generic.png
217 ms
icn_hamburger.svg
203 ms
close.png
207 ms
bttn_scrolltotop.svg
203 ms
promotional_background.webp
205 ms
logo_hoz_white.webp
233 ms
new_apps_we_love_2019.webp
239 ms
dual_screenshot.webp
275 ms
Download_on_the_App_Store_Badge_US-UK_RGB_blk_092917.svg
212 ms
inc-logo.svg
210 ms
grammy.svg
207 ms
forbes.svg
842 ms
huffpost.svg
234 ms
words_wall_bg_xl.webp
368 ms
words_wall_sm.webp
274 ms
words_wall_md.webp
270 ms
words_wall_lg.webp
319 ms
words_wall_xl.webp
369 ms
inspire.png
467 ms
icn_inspire.svg
425 ms
icn_relax.svg
456 ms
icn_grow.svg
400 ms
breakdown_bg.webp
654 ms
breakdown_screenshot.webp
454 ms
stars.png
532 ms
footer_bg.webp
513 ms
social-f.svg
516 ms
social-twit.svg
508 ms
social-insta.svg
582 ms
en_badge_web_generic.png
30 ms
sdk.js
10 ms
fontawesome-webfont.woff
109 ms
humm.ly accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
humm.ly 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
Browser errors were logged to the console
Page has valid source maps
humm.ly SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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 Humm.ly 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 Humm.ly 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.
humm.ly
Open Graph data is detected on the main page of Humm. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: