4.1 sec in total
208 ms
3.2 sec
673 ms
Welcome to octo.ly homepage info - get ready to check Octo best content right away, or after learning these important things about octo.ly
Connect with vetted influencers and consumers for authentic product reviews across social media and eCommerce platforms
Visit octo.lyWe analyzed Octo.ly page load time and found that the first response time was 208 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
octo.ly performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value5.4 s
20/100
25%
Value3.1 s
93/100
10%
Value850 ms
33/100
30%
Value0.164
72/100
15%
Value9.9 s
27/100
10%
208 ms
44 ms
61 ms
273 ms
552 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Octo.ly, 8% (5 requests) were made to Octoly.wufoo.com and 8% (5 requests) were made to Js.intercomcdn.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Octoly.wufoo.com.
Page size can be reduced by 577.8 kB (42%)
1.4 MB
799.9 kB
In fact, the total size of Octo.ly main page is 1.4 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. 45% of websites need less resources to load. Images take 601.9 kB which makes up the majority of the site volume.
Potential reduce by 149.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 149.6 kB or 84% of the original size.
Potential reduce by 19.4 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. Octo images are well optimized though.
Potential reduce by 223.7 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 223.7 kB or 61% of the original size.
Potential reduce by 185.0 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. Octo.ly needs all CSS files to be minified and compressed as it can save up to 185.0 kB or 81% of the original size.
Number of requests can be reduced by 26 (45%)
58
32
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Octo. 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 4 to 1 for CSS and as a result speed up the page load time.
www.octoly.com
208 ms
home-2595e0849ccaa141c9803f0a81900809f173121a53cffd64dc9e4b23d11114a8.css
44 ms
front-52f9be33c7f51351afc0b4119e8623e07fc6c94775676c9919223032c26fc63b.js
61 ms
analytics.min.js
273 ms
Q7SynsCoMNl1.jpg
552 ms
form.js
550 ms
c2c.min.js
117 ms
logo_white-89cbd89658bb860e57f432589871de5e24c5cb28df41bf9b4ce5830793b0b21b.png
31 ms
cover-lg-bde14f7662a4e05ec7374cd69f458a48f1e8f8ed123618ee63b5698b5af1ceaf.jpg
96 ms
step-1-043d52f882f58b24b7be95c95357b84696225e9db05661283f5d22f7042721a4.png
59 ms
step-2-71c347c7e272cba961692aa4cda52b3ad81ab45a3f8e7274c20ede0a4e21b536.png
59 ms
step-3-c1f8cf597cd9dc46559e041a99321bceb99432886a63c03e19df5e02f04704d9.png
58 ms
sigma-8c3c71182243cbc2aa436ef29ba2130180794ca592aa742e765c40f1e493ed96.png
59 ms
lancome-3d8856767eca107dc4949b351b5ac5534bfbb8a6f66db52b7cf6f1ea257bfe91.png
59 ms
makeup_for_ever-f11400b870f7be1e50f7de8bd70d2c740c69477b010a845edb53208bdde67f10.png
69 ms
loreal_paris-b785cb48466dda4a61e2ebd676ea1b63c1172bd1ba263271fae588c008d8b402.png
64 ms
maybelline-97b28199c85ac8c8d611a4ba693df7a2ac24f026cc6b7e0bef2a2fed8fd9c159.png
65 ms
ud-9edd9e48d7fced044bce7ad62b91add9d62ae37c45759f4d4f12b4bdb86bbf42.png
65 ms
sisley-807c654c8edefb34bd8a01b60bf759a50ed512431f6751487a3f4d67dc9ef1e5.png
65 ms
and_more-e16a8d839d2e8312a1a12523c710fea47c90da101dd437e4e6e750338517eff0.png
69 ms
products-sm-42ca00f724e9ff30e130fdf00d1298b02c98dd10b34a88640ef0f85b4f60cb78.png
75 ms
passion-section-sm-d5a2b1ef29bc0ae1ad362f98fa46adb6005502acdef32465d45b1d2df055867e.png
75 ms
what-youtubers-say-about-us-cover-lg-a42c533ecf3f3f326ac40458ad7e9df1f0fee80c919333e3e2ea48ef01bbff68.jpg
139 ms
ihascupquake-pic-42a2eeaf67741f62ff5a1bf20a8a11a0e7fcda42f3e67c386c1730221821f79c.png
74 ms
mikumikujinx-pic-a7b4954398c4bd1043f35239c5129f5a876dea371f8dea206cb48b0e56bb0b0a.png
72 ms
cover-1-ab5eddf96d39e32c720030e5d23025037fafe97dd2872854b55b6a2519a572a3.jpg
81 ms
cover-2-b3ce3866ee8018b84fc41851fd098b506ed4a711258882000797e876d861657b.jpg
86 ms
cover-3-08bf98b47c69f85cee27e12e5f316ff5d288c4802043db8ba021d838c9be8ff0.jpg
87 ms
logo_footer-c38ca69425ecad85cd847ab2a493c70ffc4c1d69d5a514c1cf5e73a0ac41337d.png
79 ms
JybKdtcFv0Gf.jpg
634 ms
LCDwqZ21
634 ms
ProximaNova-Regular-2b80fbe521e07e4e84eb52e707b364c3e6c05c57e483276dc4b3be93a9794ba9.otf
97 ms
ProximaNova-Bold-b9e81a47aecd3d05445ae775f48d08b3de46b2039f1d229a58a87be194e327ec.otf
97 ms
ProximaNovaACond-Black-aa63c4184f5e2b30ee06999a09beee343d5930812cc64aacfa439bc117765c23.otf
90 ms
fontawesome-webfont-c812ddc9e475d3e65d68a6b3b589ce598a2a5babb7afc55477d59215c4a38a40.woff
134 ms
p
600 ms
adsct
174 ms
i
599 ms
conversion_async.js
121 ms
fbevents.js
249 ms
analytics.js
126 ms
fpmmh3lr
160 ms
696723.js
159 ms
collect
21 ms
intercom.21a35ffd.js
97 ms
179 ms
embedKey=m1cq8h8g1fzf4of491731&entsource=&referrer=
576 ms
163 ms
ga-audiences
104 ms
echo.515e8809.js
43 ms
ping
176 ms
Screen_Shot_2015-11-04_at_15.38.26.png
71 ms
icon-launcher-acquire.8a742481.png
11 ms
client-test
147 ms
client-test
132 ms
icon-preview-close.ec1a68fc.png
13 ms
1549453_10203069730804976_457150888271596266_n.jpg
36 ms
2015_.jpg
35 ms
index.0266.css
177 ms
theme.css
295 ms
wufoo.css
4 ms
dynamic.0266.js
603 ms
icon-close-white@1x.bac0a0d6.png
19 ms
fieldbg.gif
1302 ms
ProximaNova-Bold.otf
9 ms
ProximaNova-Regular.otf
8 ms
octo.ly 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 input fields do not have accessible names
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
Image elements do not have [alt] attributes
Links do not have a discernible name
octo.ly 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
octo.ly SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Octo.ly 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 Octo.ly 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.
octo.ly
Open Graph data is detected on the main page of Octo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: