4.2 sec in total
280 ms
3.5 sec
492 ms
Visit eyeka.com now to see the best up-to-date Eyeka content for India and also check out these interesting facts you probably never knew about eyeka.com
eYeka is a global community of talented creators who love to solve brands' challenges with fresh thinking, creative ideas and shareable content.
Visit eyeka.comWe analyzed Eyeka.com page load time and found that the first response time was 280 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
eyeka.com performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value9.2 s
1/100
25%
Value7.7 s
25/100
10%
Value3,190 ms
2/100
30%
Value0.297
40/100
15%
Value10.4 s
24/100
10%
280 ms
377 ms
1105 ms
480 ms
67 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Eyeka.com, 40% (25 requests) were made to Assets.eyeka.com and 18% (11 requests) were made to S3-ie.eyeka.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source En.eyeka.com.
Page size can be reduced by 1.6 MB (60%)
2.7 MB
1.1 MB
In fact, the total size of Eyeka.com main page is 2.7 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. CSS take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 39.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 39.4 kB or 75% of the original size.
Potential reduce by 14.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. Eyeka images are well optimized though.
Potential reduce by 665.4 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 665.4 kB or 64% of the original size.
Potential reduce by 886.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. Eyeka.com needs all CSS files to be minified and compressed as it can save up to 886.0 kB or 84% of the original size.
Number of requests can be reduced by 14 (27%)
51
37
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eyeka. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
eyeka.com
280 ms
eyeka.com
377 ms
en.eyeka.com
1105 ms
application-ddd3e991adac3cb3e72c483834998ba0.css
480 ms
css
67 ms
application-9b19dd559f8a1891c370eebb35c2ce71.js
758 ms
fp.js
172 ms
oct.js
119 ms
N6Qxsdox5riGycjwO6DCA.js
52 ms
conversion.js
65 ms
ga.js
94 ms
8f4e6cd0f12f0130c1e80a1e24287e51.jpg
511 ms
a128d970084c013306950a1e243ccdfe.jpg
494 ms
5b9bcf60793649ce981ff991fa4db3b6.jpg
492 ms
ac705af045104c86bf212d111bc36b19.jpg
493 ms
ac22af51213a408686d5210bab882e82.jpg
492 ms
825a72a9a8d14e4080ded4bd11453eb8.jpg
492 ms
6eb5cedc83e8434885f4afafeae6eb36.jpg
546 ms
cb31da288bfd40c8aa75e80fa106de88.jpg
532 ms
18a712b6d76a43c085bc0dc5ad3b8dc5.jpg
533 ms
5e6783e34b454942835cb015301ad771.jpg
550 ms
9fc533bb43054e258b8ae38f2a057fe7.jpg
533 ms
eYeka-logo-99x33-82c5306d1cb8b95d0dca916abb39ea17.png
54 ms
eyeka-10-years-icon-01-1fad3e6e9cf064c780a0479ff285d96f.png
103 ms
header-background-7d5db1afbefeb411b46f9b58d2042de0.jpg
106 ms
google-play-store-eeae2dc9b3cc5b566936cb017d2665f1.png
179 ms
apple-store-05968d251dd0571a6ce94b57e8d986fb.png
196 ms
eyeka-10-years-banner-01-63107163662978101e9c4ea0cd1b657a.jpg
496 ms
presentation-connection-2884340f469cea03292f2abe6f3e24a1.jpg
438 ms
presentation-contests-background-e1ba934d5bc2e60aaa411c03d21aae52.jpg
213 ms
home-steps-background-d4f03a61c2a504110e373817890f1577.jpg
404 ms
nestle-a9410305f5fbd7ec3f43b3cebead2058.png
210 ms
coca-cola-093ae20f18ed74c0a77438e1cf004820.png
402 ms
unilever-617a9d5b72de6a7c0625c3c482874aa0.png
435 ms
microsoft-ea75c4b254950d21403102d885ad9530.png
435 ms
samsung-c4ca2efdf59e4e5ce7f23afdad453a2a.png
435 ms
aides-8ebcb032daa7fb8104e6d15e4498d0be.png
435 ms
ebay-0f7e468b91539a8d3bf8d31dd42f7efd.png
485 ms
toyota-fc45680816ca16aea075c5d22f4027ec.png
485 ms
estee-lauder-0f3914f341dad990b8d840cfd2133780.png
486 ms
adidas-3e20cb5c1ed3bb0b6d715b49cd06f177.png
484 ms
presentation-brands-background-f27da311ebc5d2a6daa44d586caa6d9b.jpg
515 ms
icon-5ad68ec9b3d76569782a5e6ca8b879cf.png
560 ms
logo-eYeka-round-32d0302fad29481a148b194dacc57f2d.svg
518 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
129 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
154 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
353 ms
fontawesome-webfont-5245cd65bc971c6552fb552c7fa355cb.woff
496 ms
__utm.gif
19 ms
collect
286 ms
fbds.js
202 ms
adsct
258 ms
adsct
277 ms
212 ms
ga-audiences
118 ms
offsite_event.php
154 ms
94 ms
33 ms
radar.js
453 ms
track.js
156 ms
21 ms
handshake.js
119 ms
eyeka.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
Buttons do not have an accessible name
Links do not have a discernible name
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
[id] attributes on active, focusable elements are not unique
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
eyeka.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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
eyeka.com 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
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
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eyeka.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 Eyeka.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
eyeka.com
Open Graph description is not detected on the main page of Eyeka. 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: