3.2 sec in total
912 ms
2 sec
342 ms
Visit rehabmusic.com now to see the best up-to-date REHAB Music content and also check out these interesting facts you probably never knew about rehabmusic.com
REHAB. 278,223 likes · 2,363 talking about this. Come out and see us! Look for shows coming to a town near you!
Visit rehabmusic.comWe analyzed Rehabmusic.com page load time and found that the first response time was 912 ms and then it took 2.3 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.
rehabmusic.com performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value4.5 s
38/100
25%
Value4.3 s
75/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value4.3 s
84/100
10%
912 ms
55 ms
55 ms
50 ms
40 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Rehabmusic.com, 29% (32 requests) were made to Scontent.xx.fbcdn.net and 3% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (912 ms) relates to the external source Facebook.com.
Page size can be reduced by 277.7 kB (29%)
963.3 kB
685.7 kB
In fact, the total size of Rehabmusic.com main page is 963.3 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. 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 628.4 kB which makes up the majority of the site volume.
Potential reduce by 269.7 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 269.7 kB or 81% of the original size.
Potential reduce by 8.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. REHAB Music images are well optimized though.
Number of requests can be reduced by 61 (55%)
111
50
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of REHAB Music. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
rehabmusic
912 ms
IWXAbM4pe57.css
55 ms
_WYx8qAOsiF.css
55 ms
whsuYM0JyRK.css
50 ms
wmiz7xzFfqO.css
40 ms
OJcLXXE4bYe.css
58 ms
eDKl-ra6OP1.css
56 ms
aDk70ZHFIl3.css
58 ms
yq2wLTItbV0.css
56 ms
yYGNrWyPiTw.css
65 ms
vR0pLYWj618.css
63 ms
v_An6I20hBD.css
62 ms
h3AvqLq2os9.css
62 ms
eXhc6OJ3pgj.css
71 ms
BzRTbh4XkpJ.css
78 ms
BViiCxy-W5p.css
79 ms
UBsaA5Ft-O6.css
79 ms
dcnr_H-EB5r.css
81 ms
q68gy-v_YMF.js
80 ms
event
459 ms
10383517_10154200620790076_6358608388934771392_n.jpg
94 ms
safe_image.php
171 ms
safe_image.php
192 ms
1911862_10153847735060076_2126010273_n.jpg
93 ms
12033243_10156037332335076_2806901062705585624_n.jpg
93 ms
10665067_10154592471105076_4251707287508939807_n.png
92 ms
10527283_10154437317430076_1754918335799545526_n.png
91 ms
1554583_10154336969985076_6145194690143256935_n.png
155 ms
10478543_10154234048555076_5788369454912390784_n.png
96 ms
10429348_10154233945440076_6269620040472569354_n.png
189 ms
10491999_10154233930690076_4630453673714427213_n.png
163 ms
10338721_10154204579630076_4853083241107552206_n.png
186 ms
10383517_10154200620790076_6358608388934771392_n.jpg
162 ms
410770_10150757337646349_10150757337041349_20178_259_b.jpg
186 ms
51555_1638722570875_1638721530849_13916_757_b.jpg
190 ms
11707497_1485022645124322_2765363960695380882_n.jpg
211 ms
10462742_10205649341223613_3883705234285541088_n.jpg
188 ms
12794462_10207898825645340_8017495542575109375_n.jpg
202 ms
10553375_10152300256107157_3466060909496286370_n.png
190 ms
600286_10151683339125907_2012610938_n.jpg
191 ms
10646922_625661747567033_7471719800104314945_n.jpg
195 ms
1911862_10153847735060076_2126010273_n.jpg
195 ms
12033243_10156037332335076_2806901062705585624_n.jpg
194 ms
LXQaqfwANV7.png
72 ms
ZVyMWStefv_.png
73 ms
K00K-UgnsKu.png
74 ms
wL6VQj7Ab77.png
71 ms
-PAXP-deijE.gif
80 ms
ZrLxvLoiUzX.png
69 ms
GsNJNwuI-UM.gif
83 ms
UHNY_g5mVbr.js
50 ms
FJmpeSpHpjS.js
90 ms
hbybLXHu6w1.js
50 ms
Oagsvfb4VWi.js
116 ms
1FCa-btixu2.js
117 ms
remhd19g416.js
140 ms
1bNoFZUdlYZ.js
141 ms
_UYztdBNTjs.js
141 ms
7BE0CZr3HTs.js
146 ms
IjqSyiwKeaX.js
153 ms
RTHSWgdzleR.js
148 ms
OZFAYTv-ZUg.js
146 ms
LTv6ZK-5zxz.js
163 ms
VfAud2trIQQ.js
153 ms
-7JBD_ybv4q.js
163 ms
HgJbVwzBr8E.js
149 ms
pQrUxxo5oQp.js
154 ms
H3EKDTObx05.js
157 ms
J0ZuTxeV0vD.js
163 ms
bh5z0Gfv2P_.js
161 ms
njEKf1WUXml.js
164 ms
1QuX41zDRrx.js
374 ms
yMCR4PoU6B-.js
374 ms
7uWMMev-gdj.js
372 ms
__xwCsHu7eq.js
373 ms
yBzWdmXwoNV.js
372 ms
jn5cerRXiQf.js
374 ms
yXuA_dMgOm6.js
377 ms
c05laeT1OPx.js
379 ms
spacer.gif
101 ms
safe_image.php
378 ms
12330626_1095830107094390_1777955124_n.png
142 ms
851593_656628887702557_1258834055_n.png
148 ms
851581_10151450532736229_2025805957_n.gif
148 ms
-sVccfRXDIY.js
348 ms
UiJCRDQUmbL.js
346 ms
450NBOJyjOf.js
348 ms
HEyyDkPknAC.png
344 ms
XKFipC8X0hA.png
350 ms
geAvKyblz0A.png
342 ms
l5aPruN9xMM.png
336 ms
YGgz9e4B0yW.png
335 ms
ZYpT1aFajd7.png
302 ms
bNvHN6v1NeH.png
282 ms
b53Ajb4ihCP.gif
274 ms
516 ms
ZPCmDKlM9R2.js
80 ms
F1Xohf2RB95.png
174 ms
I6-MnjEovm5.js
140 ms
Dppan5o6UJu.js
141 ms
8v2_hdH4Nfm.js
137 ms
-Tr757ZEtMP.js
139 ms
A0qdgknEnD5.js
138 ms
12109098_1059969500714782_2615267048080190109_n.jpg
99 ms
12345462_936943156387505_6858943264287778101_n.jpg
83 ms
12715363_603409026477360_8449451008992121855_n.jpg
88 ms
12790860_10153507817842333_4102380167025238328_n.jpg
85 ms
12196172_10207252765384846_4721619734736427617_n.jpg
86 ms
10959673_340940149449381_3278769170878927809_n.jpg
84 ms
1385839_604757123014234_606747078142396130_n.jpg
83 ms
12003888_10156041045840591_2550515007440698202_n.jpg
85 ms
aeO1ik7i7-T.png
86 ms
rehabmusic.com 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.
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.
rehabmusic.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
rehabmusic.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rehabmusic.com 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 Rehabmusic.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.
rehabmusic.com
Open Graph description is not detected on the main page of REHAB Music. 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: