2.7 sec in total
14 ms
1.7 sec
939 ms
Welcome to curious.com homepage info - get ready to check Curious best content for India right away, or after learning these important things about curious.com
Join Curious.com and get a daily learning workout with daily curios, challenging puzzles, and 25,000+ video lessons recommended just for you.
Visit curious.comWe analyzed Curious.com page load time and found that the first response time was 14 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
curious.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value5.0 s
27/100
25%
Value8.7 s
16/100
10%
Value13,330 ms
0/100
30%
Value0
100/100
15%
Value21.5 s
1/100
10%
14 ms
244 ms
91 ms
62 ms
126 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 5% of them (4 requests) were addressed to the original Curious.com, 34% (25 requests) were made to Dt6ou19bznalr.cloudfront.net and 26% (19 requests) were made to D5jbfvc8q9uxw.cloudfront.net. The less responsive or slowest element that took the longest time to load (662 ms) relates to the external source Dt6ou19bznalr.cloudfront.net.
Page size can be reduced by 1.6 MB (39%)
4.1 MB
2.5 MB
In fact, the total size of Curious.com main page is 4.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 59.4 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 59.4 kB or 74% of the original size.
Potential reduce by 29.7 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. Curious images are well optimized though.
Potential reduce by 1.0 MB
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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.0 MB or 70% of the original size.
Potential reduce by 501.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. Curious.com needs all CSS files to be minified and compressed as it can save up to 501.5 kB or 76% of the original size.
Number of requests can be reduced by 24 (34%)
71
47
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Curious. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
curious.com
14 ms
curious.com
244 ms
application-06560a49aab1ed3021071e69193cced4.css
91 ms
font-awesome.min.css
62 ms
css
126 ms
marketing_site-b2fa6671e76d96c491b502813d0fb779.css
75 ms
138 ms
head-89a8429ed39396fc9081ef14cf3ce786.js
122 ms
181125045.js
286 ms
ga.js
92 ms
analytics.js
124 ms
logo_black-a7b2d91173a39a2b69a385e16ddcf5ee.png
46 ms
marketing_site-sde694497f8-d0a41fc3685dacec01d8e0e00d6fe7ca.png
87 ms
example_curiosity-b73637f30c5e424370ace2462f01ecc1.png
54 ms
learning_wheel-856f26b914c5f82b378642151c3544de.png
63 ms
example_wheel_1-f05196f4ea85148d70a9eb92cd7c22c7.png
107 ms
example_wheel_3-f5c58e4a9b956c0515314ee7e0570aa2.png
148 ms
app_accessibility-a241566eb1d827cdba6ab6fb2b53b3ca.png
148 ms
fakies-f22080e05f595d521407125d6620236b.png
128 ms
teacher_arloa-00bd1897813f6fb570ddef7a3f9545c5.jpg
106 ms
teacher_celest-b3fa016c0925effb1e3b44f68c411433.jpg
107 ms
teacher_krista-c45dc32a79021d4942e5a89c9680177a.jpg
111 ms
teacher_kalani-bcf190fb966185fb97d12dbf68b40578.jpg
109 ms
teacher_tommacy-366f45cf0294bbc4ec542f8a7758f570.jpg
121 ms
teacher_sedie-e05f24048934f1bfa3879c80ea422f34.jpg
127 ms
teacher_canggu-867f69ae59695fd0febc327b521a8497.jpg
126 ms
teacher_oolala-352619a55e39294442a7188f59b7718c.jpg
128 ms
teacher_pattie-d631cf5633a77e0e685dafe5c8a86d0b.jpg
129 ms
teacher_sophie-96789a48e8ce463a572f98067a465da9.jpg
141 ms
teacher_brianwood-79e001db060a674550b7aac22556d05e.jpg
146 ms
lessons-c95e8c1912da4b53143d847cf2ea1fc4.jpg
302 ms
chart-0f77ab036f426ac387757fd44562bca4.png
150 ms
chart_vertical-70239e631d604bbc246ccd5473e9e0b9.png
477 ms
example_quiz-504ad1e50f198e3450007c238a6f7b71.png
104 ms
learning_funnel-459cbd23d19b66e0dd1d3a4359f55d0e.png
104 ms
learning_wheel_overlay-46c0973cb125a66e457cbdde00c4e872.png
108 ms
learning_wheel_band-e4c327bd7b0f0c5d2ae9a899ddd5b6d5.png
102 ms
example_wheel_2-d9d854a037c67ad1d7e9355b70366071.png
120 ms
teacher_hari-2edfa31a58421cab77bfbe6610490997.jpg
107 ms
teacher_ntizuchi-3dcc65d23c049bfe8687ceeb732f6924.jpg
118 ms
teacher_chriscalder-397dd53c41f722d5d503f12246de4443.jpg
107 ms
teacher_ubloom-8fd115752cc733fbc35352ee72e877a9.jpg
118 ms
teacher_catecosta-81017f581f82e10c4124cb51c1fb5d4d.jpg
122 ms
teacher_mimig-7dad61af3a51b888978e0b66f21fff22.jpg
122 ms
teacher_dzung-756113af96437c8175c19522a9e50b51.jpg
120 ms
teacher_oneils-506d25bf3d46d90c50a49748acebcc1d.jpg
144 ms
teacher_chuck-65722de30520102e2665acaafae916a0.jpg
141 ms
teacher_tfunke-1f33a91fe06b8a3b39939b57dc37cb98.jpg
140 ms
teacher_learntoprogram-a64df1d9e9db53dd673c4e9f2e113724.jpg
141 ms
mountains_background-421f91123d44db03df3634a1a84ff6ae.jpg
130 ms
logo_white-ac5c4bfdf3e344c2ade1271196c62bef.png
662 ms
marketing_site-1c18898e4550fffa9d6c24e12e3d6dd5.js
139 ms
widgets.js
318 ms
plusone.js
130 ms
sdk.js
531 ms
oct.js
358 ms
channel.html
54 ms
__utm.gif
51 ms
ec.js
12 ms
collect
19 ms
collect
40 ms
collect
175 ms
cb=gapi.loaded_0
5 ms
fbds.js
68 ms
adsct
113 ms
adsct
116 ms
121 ms
xd_arbiter.php
435 ms
78 ms
nr-885.min.js
51 ms
30 ms
xd_arbiter.php
339 ms
f327343bc4
118 ms
curious.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
curious.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
curious.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Curious.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 Curious.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.
curious.com
Open Graph data is detected on the main page of Curious. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: