1.4 sec in total
131 ms
816 ms
417 ms
Welcome to 3blue1brown.com homepage info - get ready to check 3Blue1Brown best content for United States right away, or after learning these important things about 3blue1brown.com
Mathematics with a distinct visual perspective. Linear algebra, calculus, neural networks, topology, and more.
Visit 3blue1brown.comWe analyzed 3blue1brown.com page load time and found that the first response time was 131 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
3blue1brown.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value8.9 s
1/100
25%
Value6.8 s
35/100
10%
Value2,460 ms
4/100
30%
Value0.192
64/100
15%
Value18.7 s
3/100
10%
131 ms
19 ms
62 ms
63 ms
80 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 29% of them (34 requests) were addressed to the original 3blue1brown.com, 54% (63 requests) were made to Substackcdn.com and 7% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (394 ms) belongs to the original domain 3blue1brown.com.
Page size can be reduced by 254.5 kB (41%)
626.2 kB
371.7 kB
In fact, the total size of 3blue1brown.com main page is 626.2 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. 70% of websites need less resources to load. HTML takes 314.1 kB which makes up the majority of the site volume.
Potential reduce by 244.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. 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 244.2 kB or 78% of the original size.
Potential reduce by 3.8 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. 3Blue1Brown images are well optimized though.
Potential reduce by 33 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 6.5 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. 3blue1brown.com has all CSS files already compressed.
Number of requests can be reduced by 78 (76%)
102
24
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 3Blue1Brown. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 63 to 1 for CSS and as a result speed up the page load time.
3blue1brown.com
131 ms
3blue1brown.com
19 ms
www.3blue1brown.com
62 ms
all.css
63 ms
js
80 ms
b165666056315602.css
228 ms
dc74d41d53a5d01c.css
238 ms
polyfills-c67a75d1b6f99dc8.js
394 ms
webpack-2803c7b99464701e.js
388 ms
framework-67ffd913504c6fc8.js
32 ms
main-5bd8c83b552524a4.js
32 ms
_app-81c54062c81fe22a.js
38 ms
b5f2ed29-d9b46a1360638323.js
38 ms
200-dd9f7920ffe4362a.js
47 ms
929-c698770cad9b0490.js
49 ms
index-5eb7f72bd57c2c86.js
51 ms
_buildManifest.js
50 ms
_ssgManifest.js
51 ms
maxresdefault.jpg
49 ms
embed
115 ms
pi-comment.svg
20 ms
calculus.svg
23 ms
linear-algebra.svg
24 ms
neural-networks.svg
26 ms
differential-equations.svg
34 ms
puzzles.svg
31 ms
why-pi.svg
37 ms
geometry.svg
38 ms
analysis.svg
41 ms
physics.svg
43 ms
probability.svg
53 ms
computer-science.svg
45 ms
topology.svg
47 ms
group-theory.svg
49 ms
epidemics.svg
54 ms
lockdown-math.svg
56 ms
some.svg
58 ms
patreon-logo.svg
59 ms
entry-73201f3b.css
56 ms
index-2caf47c8.css
56 ms
responsive_img-51b02764.css
54 ms
FlexBox-9653b903.css
52 ms
free_email_form-a84f1e43.css
57 ms
Modal-507c84e7.css
57 ms
createComponent-f90fb756.css
77 ms
ElevatedTheme-4e706070.css
177 ms
app_install_modal-df86e702.css
177 ms
facepile-ae05a93f.css
77 ms
ProfileHoverCard-8ea7be39.css
177 ms
HoverCard-9fe4e916.css
180 ms
Menu-b8c38d19.css
181 ms
UserBadge-d10c54cf.css
183 ms
Tooltip-d0af0cf2.css
183 ms
Avatar-21e4510c.css
182 ms
Select-1e64850c.css
183 ms
IntroPopup-a01e8e94.css
185 ms
SectionPageContainer-cc32eba2.css
184 ms
NavbarUserWidget-63813d75.css
189 ms
homepage_hooks-1b33585e.css
187 ms
sortBy-fe5c4c56.css
187 ms
Progress-3aee957a.css
188 ms
recentSurfaces-fa9efc75.css
190 ms
user_indicator-e7037a0a.css
189 ms
ShareableImageModal-6a735338.css
191 ms
Switch-99aff950.css
193 ms
Button-8514f63d.css
192 ms
PubAccentTheme-e486b485.css
190 ms
overflow_menu-db9a534e.css
193 ms
newsletter_item_list-03468b3d.css
194 ms
CreditCardIcon-d7e0cff2.css
194 ms
ProfileSetupToast-b1d1db47.css
197 ms
CommunityPostView-26824100.css
196 ms
Attachments-5958cf02.css
194 ms
CommentBody-984c6bbf.css
197 ms
6c2ff3e3828e4017b7faf7b63e24cdf8.min.js
174 ms
beacon.min.js
201 ms
AlertDialog-9ade601d.css
151 ms
uniq-b886ec82.css
149 ms
Popover-6a0c224a.css
149 ms
ChatPage-3c675abd.css
150 ms
ChatAppUpsell-5a642ab8.css
150 ms
post-3cd5a9c4.css
149 ms
iterator-a23ad7ec.css
131 ms
0QI6MX1D_JOuGQbT0gvTJPa787weuyJF.woff
196 ms
0QI6MX1D_JOuGQbT0gvTJPa787wsuyJF.woff
244 ms
0QI6MX1D_JOuGQbT0gvTJPa787zAvCJF.woff
245 ms
0QI6MX1D_JOuGQbT0gvTJPa787z5vCJF.woff
247 ms
mention-981bc9fe.css
130 ms
ImageViewerModal-3811bdd5.css
86 ms
VideoVerticalMenu-a9e51cc8.css
79 ms
Recipe-796f9114.css
84 ms
recommend_linked_publication_modal-f03dfb3f.css
78 ms
AuditionPlayer-5637d633.css
80 ms
SectionLogo-44ead5a1.css
81 ms
TabBar-7430851f.css
81 ms
comments_page-83ec46a1.css
81 ms
RewardBox-5297e7a9.css
81 ms
Field-6e53593d.css
79 ms
Radio-736388f9.css
80 ms
Logo-8a4d9999.css
78 ms
FilePicker-011ef325.css
83 ms
setup_all_podcasts-9189be33.css
82 ms
CookieConsentFooter-0d9aca19.css
82 ms
main.548d4784e25e1f055dfd.css
93 ms
main-03088143.js
126 ms
https%3A%2F%2Fbucketeer-e05bbc84-baa3-437e-9518-adb32be77984.s3.amazonaws.com%2Fpublic%2Fimages%2F60fd31d6-8910-4b40-aa3d-f84f0605174e_1024x1024.png
128 ms
https%3A%2F%2Fsubstack.com%2Fimg%2Fsubstack_wordmark.black.png
127 ms
pxiEyp8kv8JHgFVrFJM.woff
115 ms
pxiByp8kv8JHgFVrLGT9V1g.woff
116 ms
pxiByp8kv8JHgFVrLEj6V1g.woff
117 ms
pxiByp8kv8JHgFVrLCz7V1g.woff
118 ms
fa-brands-400.ttf
74 ms
fa-solid-900.ttf
171 ms
fa-regular-400.ttf
170 ms
bundle.es5.min.js
36 ms
datadog-rum.js
28 ms
3blue1brown.com accessibility score
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
Form elements do not have associated labels
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
3blue1brown.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
Browser errors were logged to the console
Page has valid source maps
3blue1brown.com 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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 3blue1brown.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 3blue1brown.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.
3blue1brown.com
Open Graph data is detected on the main page of 3Blue1Brown. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: