2.5 sec in total
594 ms
1.6 sec
285 ms
Click here to check amazing 21 Days content. Otherwise, check out these important facts you probably never knew about 21days.com
Read writing from Elijah Szasz on Medium. Elijah runs a LA/SLC creative agency focused on the good side of technology. He’s also a mediocre athlete, father, and entrepreneur. https://www.spark6.com/.
Visit 21days.comWe analyzed 21days.com page load time and found that the first response time was 594 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
21days.com performance score
name
value
score
weighting
Value2.5 s
69/100
10%
Value7.9 s
3/100
25%
Value9.0 s
14/100
10%
Value3,700 ms
1/100
30%
Value0.472
18/100
15%
Value14.6 s
8/100
10%
594 ms
58 ms
25 ms
86 ms
199 ms
Our browser made a total of 33 requests to load all elements on the main page. We found that 9% of them (3 requests) were addressed to the original 21days.com, 48% (16 requests) were made to Use.typekit.net and 27% (9 requests) were made to Static1.squarespace.com. The less responsive or slowest element that took the longest time to load (594 ms) belongs to the original domain 21days.com.
Page size can be reduced by 79.4 kB (29%)
271.0 kB
191.6 kB
In fact, the total size of 21days.com main page is 271.0 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. 45% of websites need less resources to load. Images take 189.2 kB which makes up the majority of the site volume.
Potential reduce by 66.0 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 8.9 kB, which is 11% 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 66.0 kB or 81% of the original size.
Potential reduce by 13.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. 21 Days images are well optimized though.
Number of requests can be reduced by 6 (33%)
18
12
The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 21 Days. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
21days.com
594 ms
vpYJhVhCU1oUUuJ8V6NGDiZDH84x2nJG27iDESwbj29fen9ffFHN4UJLFRbh52jhWD9kFhwUFAmRZQsKweJtFewUZAbawh9UwsTLwRBqjW8DOcFzdPUaiaS0wRBqjW8DOcFzdPUCdhFydeyzSabCZAUT-cBGOWFEjWFEO1FUiABkZWF3jAF8OcFzdP37OcmC-ATy-fuDpcBDpKoDSWmyScmDSeBRZPoRdhXK2YgkdayTdAIldcNhjPG4fHCgIMMjMPMfH6qJnMIbMg6OJMJ7fbRKHyMMeMw6MKG4f5w7IMMj2PMfH6qJn3IbMg6IJMJ7fbK3MsMMeMt6MKG4fHXgIMMjgKMfH6qJn6IbMg6bJMJ7fbKOMsMMeMS6MKG4fJ3gIMMjIPMfH6qJ7bIbMg6JJMJ7fbK7MsMMegJ6MKG4fJqgIMMjfPMfH6qJK6IbMg6QJMHbM-1Vk_MB.js
58 ms
css
25 ms
86 ms
21days.com
199 ms
common-c2cb21af65f6d18bb4c6-min.js
59 ms
commerce-cf5ca5fa5feb9716f7f4-min.js
37 ms
commerce-7f4130fee43d9b486ac93410db2112d3-min.css
26 ms
site.css
30 ms
social-accounts.svg
205 ms
202 ms
icon-searchqueries-20-dark.png
202 ms
block-indicator-dark.png
202 ms
RecordHit
277 ms
15 ms
Zh5r25ARMZ8rfY1Piu1rM0PozEbdFcGLyXSqcZf6Yj6ffOAREN32IgCjMKM2HMJtM3.woff
28 ms
hCVvsRTUKDJOgMwfK8xY-zXLcnH34Yq5lKzYBDMehvtffOhREN32IgCjMKM2HMJtMb.woff
73 ms
ypvk_yI2b-_vul5TuOuCZyV2eGRIe_yhSVroliFb0uCffOcREN32IgCjMKM2HMJtgM.woff
123 ms
sZqw0BeOokIUXxHaXeJCmT6us5b-fw1GREgUAYifXAqffO0REN32IgCjMKM2HMJtg6.woff
149 ms
iFtCRXuGomJGndf054Mx1oyo2-w8vbrtQykkKmKtBuwffOeREN32IgCjMKM2HMJtg3.woff
166 ms
90Os1WQYOzXn14sPoPwvT94XnZ-Lj8cRawFxvbrkCRjffO5REN32IgCjMKM2HMJtfM.woff
166 ms
dgDiodgawpxOH-HxC7W9boSKPy4DOKMslSn8huYnjhXffHrREN32IgCjMKM2HMJtfb.woff
165 ms
0jy7OQTIhMkCdK0oczhImj9i8C3QSRmxfh6p5h-3G6qffO7REN32IgCjMKM2HMJt26.woff
165 ms
xqVP_NlehvgpJO5h_V34xXezRxrbA32DzQeKgbWOwj3ffO-REN32IgCjMKM2HMJt2b.woff
152 ms
eEz9g_9rffkCFnCz-m4hWBw7yz5s4qlfnmBYBBdZFrXffOEREN32IgCjMKM2HMJtf3.woff
180 ms
pCd-eSxohJzlFG_mee9Rq96Hk8NChPkZPrZV8D98qnjffOkREN32IgCjMKM2HMJtIM.woff
180 ms
FPSxGKpQSYNMa2DaoLxRzUPuCX7OhtO9wpajvAWtLGwffOHREN32IgCjMKM2HMJtIb.woff
191 ms
6-De3LrFTse0zpnJGFz6DI-zD_WTbOTAHFg5VCDeVwjffOPREN32IgCjMKM2HMJtI6.woff
191 ms
Fgblcw2ZBBZyou4ZuGTbvANKw4T2df8EXLkIJ8nuzK3ffOfREN32IgCjMKM2HMJtI3.woff
191 ms
60 ms
47 ms
27 ms
p.gif
136 ms
21days.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
[role]s are not contained by their required parent element
ARIA tooltip elements do not have accessible names.
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
Links do not have a discernible name
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.
21days.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
21days.com SEO score
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 21days.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 21days.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.
21days.com
Open Graph data is detected on the main page of 21 Days. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: