1.4 sec in total
144 ms
1.1 sec
162 ms
Welcome to curius.co homepage info - get ready to check Curius best content right away, or after learning these important things about curius.co
Curius Images for curious people. Search for the most popular free images, annotated and explained to tell a visual story. High-quality Creative Commons photos and other free images.
Visit curius.coWe analyzed Curius.co page load time and found that the first response time was 144 ms and then it took 1.3 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.
curius.co performance score
144 ms
110 ms
26 ms
527 ms
30 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 27% of them (11 requests) were addressed to the original Curius.co, 29% (12 requests) were made to Curiusbuckets3.s3.amazonaws.com and 20% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (527 ms) belongs to the original domain Curius.co.
Page size can be reduced by 368.3 kB (21%)
1.8 MB
1.4 MB
In fact, the total size of Curius.co main page is 1.8 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.4 MB which makes up the majority of the site volume.
Potential reduce by 24.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. This page needs HTML code to be minified as it can gain 4.3 kB, which is 14% 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 24.4 kB or 79% of the original size.
Potential reduce by 101.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. Curius images are well optimized though.
Potential reduce by 58.5 kB
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 58.5 kB or 48% of the original size.
Potential reduce by 184.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. Curius.co needs all CSS files to be minified and compressed as it can save up to 184.4 kB or 85% of the original size.
Number of requests can be reduced by 10 (36%)
28
18
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Curius. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
curius.co
144 ms
feed
110 ms
css
26 ms
style.css
527 ms
normalise.css
30 ms
foundation-icons.css
126 ms
font-awesome.min.css
5 ms
jquery.min.js
24 ms
vote.js
30 ms
ie-emulation-modes-warning.js
33 ms
bootstrap.min.js
44 ms
ie10-viewport-bug-workaround.js
36 ms
analytics.js
25 ms
airbnb_logo_detail_small_23a526_withtext_8972e_cdc801_thumb_0b52a.jpg
201 ms
transparent-uber_19d63f_withtext_f536c_21807d_thumb_2d02c.jpg
175 ms
shazam-listening-195x129_b5e6b6_withtext_e4c48_e1790e_thumb_2fe39.jpg
202 ms
Gods-to-do-scroll-600tall_long_scroll2_2f8888_withtext_e72c7_9f7e3b_thumb_18403.jpg
185 ms
Gods-to-do-scroll-600tall_long_scroll2_2f8888_withtext_b88be_7abdb1_thumb_18348.jpg
184 ms
Gods-to-do-scroll-600tall_long_scroll2_2f8888_withtext_42293_3513ce_thumb_c560f.jpg
266 ms
notsozen_bnw_beach_warrior_98a91a_withtext_39a08_369da5_thumb_2c47f.jpg
213 ms
notsozen_bnw_beach_warrior_98a91a_withtext_99fef_520009_thumb_270d2.jpg
247 ms
notsozen_bnw_beach_warrior_98a91a_withtext_604c2_f0d8af_thumb_f34c2.jpg
223 ms
TEDTALKS-NET_884edf_thumb_99dc3.jpg
265 ms
tedtalks-sharia_ee023f_thumb_43cc9.jpg
276 ms
tedtalks-marriage_beb238_thumb_ee8cc.jpg
272 ms
MViwy4K6e56oHcyeMzjbCQ.ttf
73 ms
F-uvpIj1hF17IDyvQvI50Q.ttf
118 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
118 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
117 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
118 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
117 ms
monoton-regular-webfont.woff
94 ms
ceRJlaOl8VqdbfWAlFaxNQ.ttf
113 ms
Audiowide.woff
36 ms
8XtYtNKEyyZh481XVWfVOqCWcynf_cDxXwCLxiixG1c.ttf
134 ms
fontawesome-webfont.woff
38 ms
sdk.js
63 ms
collect
48 ms
139 ms
xd_arbiter.php
38 ms
xd_arbiter.php
50 ms
curius.co SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Curius.co 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 Curius.co 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.
curius.co
Open Graph description is not detected on the main page of Curius. 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: