1.4 sec in total
70 ms
835 ms
472 ms
Visit imcurious.co now to see the best up-to-date Im Curious content and also check out these interesting facts you probably never knew about imcurious.co
Each month, we send your random and curated newsletters directly to your inbox, so you can stay curious for free!
Visit imcurious.coWe analyzed Imcurious.co page load time and found that the first response time was 70 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.
imcurious.co performance score
name
value
score
weighting
Value2.5 s
65/100
10%
Value3.4 s
66/100
25%
Value3.0 s
94/100
10%
Value80 ms
99/100
30%
Value0.044
99/100
15%
Value5.5 s
71/100
10%
70 ms
104 ms
185 ms
46 ms
52 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Imcurious.co, 53% (26 requests) were made to Fonts.gstatic.com and 24% (12 requests) were made to Uploads-ssl.webflow.com. The less responsive or slowest element that took the longest time to load (237 ms) relates to the external source Uploads-ssl.webflow.com.
Page size can be reduced by 186.8 kB (33%)
567.9 kB
381.1 kB
In fact, the total size of Imcurious.co main page is 567.9 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. Images take 362.4 kB which makes up the majority of the site volume.
Potential reduce by 11.6 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 11.6 kB or 75% of the original size.
Potential reduce by 173.9 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. Obviously, Im Curious needs image optimization as it can save up to 173.9 kB or 48% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 563 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 768 B
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. Imcurious.co has all CSS files already compressed.
Number of requests can be reduced by 4 (20%)
20
16
The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Im 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 5 to 1 for JavaScripts and as a result speed up the page load time.
imcurious.co
70 ms
imcurious.webflow.io
104 ms
imcurious.webflow.io
185 ms
imcurious.webflow.f07b09a84.css
46 ms
webfont.js
52 ms
js
119 ms
jquery-3.4.1.min.220afd743d.js
56 ms
webflow.dfceefebf.js
55 ms
css
77 ms
5efa2efc7f77d6c386ef6f70_Logo%20-%20Alternate%20Layout%20-%20Black%20(1).png
185 ms
5efa2ec6d4a785dede384286_9789-burger-menu.json
68 ms
5efa2ec6d4a78527fd384284_magnifying-glass-browser.png
82 ms
5efa2ec6d4a7857bf438428b_Component%206%20%E2%80%93%201.png
237 ms
5efa2f19771311623c8cef3d_marginalia-start-up-development.png
169 ms
5efa2f2344f50ba9f48ad399_marginalia-love-affair.png
170 ms
5efa2f308fa32253ea4c4b01_marginalia-working.png
138 ms
5efa2ec6d4a78546dc384281_watermelon-icon.png
141 ms
5efa2ec6d4a78534bf384288_double-icon.png
169 ms
5efa2ec6d4a785484d384282_jaws-icon.png
185 ms
u-4n0qyriQwlOrhSvowK_l52xwNZWMf8.woff
68 ms
u-4n0qyriQwlOrhSvowK_l52_wFZWMf8.woff
79 ms
u-440qyriQwlOrhSvowK_l5-fCZK.woff
86 ms
u-4n0qyriQwlOrhSvowK_l521wRZWMf8.woff
93 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff
93 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aXw.woff
94 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aXw.woff
98 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff
97 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff
96 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff
97 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff
96 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aXw.woff
114 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXw.woff
115 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R8WXh0oA.woff
115 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR9WXh0oA.woff
116 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq_p9WXh0oA.woff
117 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXh0oA.woff
116 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9WXh0oA.woff
117 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq3p6WXh0oA.woff
117 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6WXh0oA.woff
118 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR6WXh0oA.woff
120 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqw16WXh0oA.woff
144 ms
u-4l0qyriQwlOrhSvowK_l5-eR7lXff4jvo.woff
117 ms
u-4m0qyriQwlOrhSvowK_l5-eRZOf-Q.woff
118 ms
u-4l0qyriQwlOrhSvowK_l5-eR71Wvf4jvo.woff
143 ms
u-4l0qyriQwlOrhSvowK_l5-eR7NWPf4jvo.woff
118 ms
webflow-badge-icon.f67cd735e3.svg
51 ms
webflow-badge-text.6faa6a38cd.svg
59 ms
analytics.js
130 ms
collect
27 ms
imcurious.co 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.
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
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
imcurious.co 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
General
Impact
Issue
Detected JavaScript libraries
imcurious.co 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imcurious.co 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 Imcurious.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.
imcurious.co
Open Graph data is detected on the main page of Im Curious. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: