3.9 sec in total
447 ms
3 sec
420 ms
Visit hmmm.com.br now to see the best up-to-date Hmmm content for Brazil and also check out these interesting facts you probably never knew about hmmm.com.br
A Hmmm Mania Geek é uma loja de presentes criativos super cool. Aqui você encontra itens irados, decoração criativa e presentes diferentes. Há mai...
Visit hmmm.com.brWe analyzed Hmmm.com.br page load time and found that the first response time was 447 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
hmmm.com.br performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value10.5 s
0/100
25%
Value8.8 s
15/100
10%
Value2,120 ms
7/100
30%
Value0.169
70/100
15%
Value26.2 s
0/100
10%
447 ms
717 ms
80 ms
96 ms
78 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 3% of them (4 requests) were addressed to the original Hmmm.com.br, 57% (78 requests) were made to Cdn.awsli.com.br and 6% (8 requests) were made to Conectiva.io. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Google.com.
Page size can be reduced by 234.7 kB (33%)
709.5 kB
474.8 kB
In fact, the total size of Hmmm.com.br main page is 709.5 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. 75% 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. Javascripts take 349.6 kB which makes up the majority of the site volume.
Potential reduce by 214.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 61.5 kB, which is 25% 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 214.2 kB or 89% of the original size.
Potential reduce by 2.6 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. Hmmm images are well optimized though.
Potential reduce by 14.7 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 3.2 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. Hmmm.com.br has all CSS files already compressed.
Number of requests can be reduced by 47 (38%)
125
78
The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hmmm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
hmmm.com.br
447 ms
www.hmmm.com.br
717 ms
all.min.css
80 ms
css2
96 ms
bootstrap-responsive.css
78 ms
style-responsive.css
77 ms
tema.css
43 ms
all.min.js
92 ms
slick.min.css
92 ms
slick.min.js
76 ms
jquery.fancybox.min.css
100 ms
jquery.fancybox.pack.min.js
101 ms
load.js
148 ms
ld.js
93 ms
__theme_custom.css
132 ms
__theme_custom.js
126 ms
avancado.css
64 ms
sdk.js
91 ms
platform.js
123 ms
owa.min.js
9 ms
analytics.js
48 ms
fbevents.js
47 ms
css
65 ms
font-awesome.min.css
81 ms
238 ms
collect
43 ms
collect
193 ms
7350bdd360.png
303 ms
fullbanner_hmmm__abril_2024__01-ibm5dzd901.jpg
305 ms
fullbanner_hmmm__abril_2024__03-q2zvdixqoc.jpg
313 ms
fullbanner_hmmm__abril_2024__02-3w67gyiono.jpg
313 ms
fullbanner_hmmm__abril_2024__04-32mjuqt6am.jpg
305 ms
246811431f5bb54f341.jpg
247 ms
246811406bd2217218d.jpg
437 ms
24681141373c26bb112.jpg
438 ms
2468419093baa7bb7e6.jpg
442 ms
246815712bb707791a8.jpg
437 ms
246840281521164b6fd.jpg
447 ms
2468402865f297948cd.jpg
452 ms
24684193172d57ca9a8.jpg
627 ms
246811420523456df1a.jpg
630 ms
246840252067790ea93.jpg
629 ms
2468402672990297853.jpg
627 ms
2468402580be2d0e2c7.jpg
628 ms
147092695d8f4e2112f.jpg
631 ms
90381095cfdf312c57.jpg
688 ms
92726201924d0b7b4d.jpg
720 ms
8dddc09d7e.jpg
718 ms
225597427c3492f01cf.jpg
729 ms
104047420720d27ecab.jpg
679 ms
91698209506983635c.jpg
734 ms
115862679dbe1acc952.jpg
788 ms
1112517771587e863dd.jpg
693 ms
193870204d9039b53b8.jpg
856 ms
171097793fe1c5326b3.jpg
786 ms
1922168408fb2794536.jpg
818 ms
111284933cf4dc32e84.jpg
866 ms
8eb45bf29b.jpg
908 ms
11590145558d8dd2b09.jpg
967 ms
1112848855f5b8c9550.jpg
794 ms
1346308795e963f7096.jpg
909 ms
17124327874e0a3a069.jpg
967 ms
193803577d8b560dd8e.jpg
1007 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
150 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
242 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
305 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
306 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
305 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
304 ms
conversion_async.js
188 ms
gtm.js
281 ms
integration.min.js
250 ms
sdk.js
21 ms
370 ms
syncframe
93 ms
fontawesome-webfont.woff
62 ms
cb=gapi.loaded_0
17 ms
cb=gapi.loaded_1
78 ms
badge
352 ms
ga-audiences
1074 ms
sdk.js
71 ms
core.js
135 ms
postmessageRelay
225 ms
event
197 ms
fontawesome-webfont.svg
624 ms
193 ms
load.js
174 ms
fontawesome-webfont.eot
608 ms
115883780344a7c0c5a.jpg
720 ms
1ec189db27.jpg
740 ms
b5b1f02f90.jpg
716 ms
217259911d62cafc294.jpg
687 ms
js
75 ms
destination
160 ms
collect
18 ms
googlelogo_color_150x54dp.png
23 ms
3604799710-postmessagerelay.js
20 ms
rpc:shindig_random.js
22 ms
182367593665a0d36b4.jpg
632 ms
1033374066941711a97.jpg
585 ms
994033526e7330d68f.jpg
738 ms
datatunnel.js
36 ms
visitor.js
37 ms
cartstackbr.js
39 ms
performa.js
44 ms
1599cb4661.jpg
596 ms
collect
19 ms
a0b8ae20f7.jpg
848 ms
31 ms
39101540cf1bb141ad.jpg
713 ms
cb=gapi.loaded_0
3 ms
ga-audiences
166 ms
180 ms
pgvw.png
139 ms
25 ms
96552806aab325a428.jpg
415 ms
799226e765.jpg
421 ms
98119492ac64ab590a.jpg
545 ms
122559723cb4d052bee.jpg
576 ms
40624353b7b36ab104.jpg
565 ms
1390980513d0fc2b01d.jpg
703 ms
29 ms
1c29ca412e.jpg
620 ms
132052855d3a132f152.jpg
681 ms
1225596592b364d6f10.jpg
646 ms
241265010f2afff8485.jpg
579 ms
225380017c5a1ae31d0.jpg
722 ms
226796360c269c23f47.jpg
672 ms
1396402211c12e70b70.jpg
724 ms
126e9a1302.jpg
704 ms
icone-pagamento.png
557 ms
pix-logo.png
553 ms
stamp_encryptssl.png
532 ms
stamp_google_safe_browsing.png
497 ms
logo-rodape-loja-pro.png
488 ms
core_rc.js
70 ms
hmmm.com.br 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
hmmm.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
hmmm.com.br 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 doesn't use legible font sizes
Tap targets are not sized appropriately
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hmmm.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Hmmm.com.br 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.
hmmm.com.br
Open Graph data is detected on the main page of Hmmm. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: