3.3 sec in total
133 ms
1.2 sec
1.9 sec
Visit 21hats.com now to see the best up-to-date 21 Hats content and also check out these interesting facts you probably never knew about 21hats.com
Get cutting-edge business advice, entrepreneurial insights & learn what it takes to run a business with 21 Hats host - Loren Feldman. Join us
Visit 21hats.comWe analyzed 21hats.com page load time and found that the first response time was 133 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
21hats.com performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value11.7 s
0/100
25%
Value6.9 s
34/100
10%
Value2,910 ms
3/100
30%
Value0
100/100
15%
Value16.3 s
5/100
10%
133 ms
210 ms
65 ms
125 ms
21 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 20% of them (18 requests) were addressed to the original 21hats.com, 70% (62 requests) were made to Substackcdn.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (477 ms) belongs to the original domain 21hats.com.
Page size can be reduced by 328.6 kB (38%)
872.1 kB
543.5 kB
In fact, the total size of 21hats.com main page is 872.1 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. 60% of websites need less resources to load. HTML takes 344.3 kB which makes up the majority of the site volume.
Potential reduce by 319.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 100.5 kB, which is 29% 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 319.2 kB or 93% of the original size.
Potential reduce by 224 B
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 Hats images are well optimized though.
Potential reduce by 674 B
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 8.4 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. 21hats.com has all CSS files already compressed.
Number of requests can be reduced by 69 (85%)
81
12
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 21 Hats. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 60 to 1 for CSS and as a result speed up the page load time.
21hats.com
133 ms
21hats.com
210 ms
js
65 ms
js
125 ms
autoptimize_0a25a80d15a0cc1e2a2fed773d267492.css
21 ms
jquery.min.js
234 ms
page.js
29 ms
lazysizes.min.js
22 ms
autoptimize_f62cb11a440f62d1f3500d02376ca753.js
477 ms
js
48 ms
embed
253 ms
dots-square.svg
136 ms
Ami-Kassar-on-SBA-loans.jpg
137 ms
play-orange.svg
136 ms
sm.25.html
63 ms
eso.Ep5bSEmr.js
143 ms
poppins-v15-latin-regular.woff
336 ms
poppins-v15-latin-500.woff
334 ms
poppins-v15-latin-700.woff
244 ms
roboto-v20-latin-regular.woff
29 ms
roboto-v20-latin-500.woff
244 ms
roboto-v20-latin-700.woff
335 ms
entry-0a24dbeb.css
122 ms
index-7d90c62b.css
129 ms
FlexBox-c95e92d2.css
134 ms
experimentsAndSiteConfigContext-cda68176.css
137 ms
Modal-8214dc28.css
141 ms
_defineProperty-e9841d58.css
140 ms
Tooltip-d4ad588b.css
140 ms
Badge-6f531bff.css
138 ms
app_install_modal-1b80d39d.css
139 ms
IntroPopup-75117138.css
144 ms
NavbarUserWidget-b3241743.css
143 ms
user_indicator-9d97d395.css
141 ms
Divider-9513d03e.css
145 ms
NotificationsDropdown-0a30d73f.css
142 ms
Menu-db1fc4e5.css
142 ms
ButtonGroup-90000653.css
145 ms
_baseEach-bef05019.css
146 ms
Toast-b371486f.css
147 ms
ProfileHoverCard-258e4bdf.css
146 ms
HoverCard-582c75ec.css
150 ms
UserBadge-fb9c174e.css
150 ms
Popover-fd5fa324.css
152 ms
AnimateHeight-6809a859.css
155 ms
Select-cd38999e.css
151 ms
video_player-01683910.css
152 ms
Input-51cc0269.css
153 ms
PressKitImage-8a8ed57a.css
158 ms
Textarea-7ab185be.css
155 ms
ShareableImageModal-4e616c35.css
155 ms
ShareAssetButtons-44463ef6.css
155 ms
overflow_menu-63853454.css
156 ms
newsletter_item_list-03468b3d.css
157 ms
ProfileSetupToast-60e0a843.css
159 ms
PublicationThreadAppLinkPage-0d6f4128.css
159 ms
CommunityPostView-18a3c6bd.css
157 ms
ImageGroup-c55cfff6.css
159 ms
6c2ff3e3828e4017b7faf7b63e24cdf8.min.js
124 ms
beacon.min.js
216 ms
bg-home.jpg
105 ms
logo.svg
110 ms
search.svg
134 ms
mention-e43b25a5.css
43 ms
context-ce20e400.css
37 ms
post-ea464af1.css
34 ms
TextLink-f399b628.css
29 ms
FollowPrompt-a56b28dc.css
29 ms
facepile-482dcc40.css
28 ms
AlertDialog-714d719c.css
28 ms
Attachments-89507aec.css
27 ms
ImageViewerModal-6e193260.css
30 ms
Field-cea155ef.css
27 ms
Tab-0cac07d2.css
29 ms
autocomplete_results-58e558b6.css
28 ms
recommend_linked_publication_modal-6be194c2.css
28 ms
PostPreviewCoverImage-70dddbb6.css
29 ms
setup_all_podcasts-839ef6d2.css
29 ms
RewardBox-5297e7a9.css
28 ms
Radio-8a0d4f75.css
28 ms
Logo-f0548763.css
26 ms
FilePicker-ceb0fe25.css
27 ms
CookieConsentFooter-0d9aca19.css
26 ms
TabBar-05c8b61f.css
26 ms
main.6bd406cc065ec3120f2e.css
26 ms
color_links.33eb7c3bd37d78bc2dc3.css
23 ms
main-676703bf.js
24 ms
https%3A%2F%2Fbucketeer-e05bbc84-baa3-437e-9518-adb32be77984.s3.amazonaws.com%2Fpublic%2Fimages%2Fa3c3bcc3-7e93-4c9a-ab72-bcaf31a34aea_512x512.png
67 ms
https%3A%2F%2Fsubstack.com%2Fimg%2Fsubstack_wordmark.black.png
66 ms
21hats.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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
21hats.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
21hats.com SEO score
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
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 21hats.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 21hats.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.
21hats.com
Open Graph data is detected on the main page of 21 Hats. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: