Tools & Wizards About Us
cookee.io screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

cookee.io

Cookee App Development Company in Perinthalmanna | Mobile App Development Company India

Page Load Speed

3.4 sec in total

First Response

773 ms

Resources Loaded

2 sec

Page Rendered

602 ms

cookee.io screenshot

About Website

Click here to check amazing Cookee content. Otherwise, check out these important facts you probably never knew about cookee.io

Become a Millionaire with your App Idea - Grow your Business faster with mobile Apps, We build high-quality Apps that can hold millions of users at a time.

Visit cookee.io

Key Findings

We analyzed Cookee.io page load time and found that the first response time was 773 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

cookee.io performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value5.2 s

59/100

10%

TBT (Total Blocking Time)

Value600 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.43

22/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

cookee.io

773 ms

bootstrap.min.css

178 ms

font-awesome.min.css

47 ms

aos.css

49 ms

font.css

359 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 80% of them (75 requests) were addressed to the original Cookee.io, 4% (4 requests) were made to Googletagmanager.com and 3% (3 requests) were made to . The less responsive or slowest element that took the longest time to load (773 ms) belongs to the original domain Cookee.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 120.0 kB (8%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cookee.io 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. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 58.6 kB

  • Original 75.0 kB
  • After minification 59.5 kB
  • After compression 16.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 15.5 kB, which is 21% 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 58.6 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 24.4 kB

  • Original 1.1 MB
  • After minification 1.0 MB

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. Cookee images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 20.7 kB

  • Original 77.0 kB
  • After minification 77.0 kB
  • After compression 56.3 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 20.7 kB or 27% of the original size.

CSS Optimization

-7%

Potential reduce by 16.3 kB

  • Original 239.9 kB
  • After minification 239.9 kB
  • After compression 223.6 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. Cookee.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (18%)

Requests Now

89

After Optimization

73

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cookee. 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 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

cookee.io

cookee.io

773 ms

bootstrap.min.css

bootstrap.min.css

178 ms

font-awesome.min.css

font-awesome.min.css

47 ms

aos.css

aos.css

49 ms

font.css

font.css

359 ms

slick.css

slick.css

127 ms

custom.css

custom.css

129 ms

bootstrap-notify.min.css

bootstrap-notify.min.css

45 ms

js

js

80 ms

js

js

131 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

26 ms

notify.js

notify.js

74 ms

popper.min.js

popper.min.js

23 ms

bootstrap.min.js

bootstrap.min.js

180 ms

aos.js

aos.js

16 ms

slick.js

slick.js

195 ms

js

js

197 ms

js

js

246 ms

analytics.js

analytics.js

236 ms

loader.gif

loader.gif

203 ms

email.svg

email.svg

201 ms

phone.svg

phone.svg

200 ms

logo.svg

logo.svg

202 ms

banner.svg

banner.svg

203 ms

client_01.jpg

client_01.jpg

203 ms

client_02.jpg

client_02.jpg

203 ms

client_03.jpg

client_03.jpg

273 ms

client_04.jpg

client_04.jpg

270 ms

client_05.jpg

client_05.jpg

273 ms

client_06.jpg

client_06.jpg

272 ms

app-store.svg

app-store.svg

273 ms

playstore.svg

playstore.svg

270 ms

shjc.jpg

shjc.jpg

385 ms

4Kids.png

4Kids.png

386 ms

tajmahal.png

tajmahal.png

445 ms

wer2.png

wer2.png

319 ms

swift.png

swift.png

319 ms

apple.svg

apple.svg

319 ms

xcode.png

xcode.png

332 ms

flutter.png

flutter.png

333 ms

pwa.png

pwa.png

333 ms

java.png

java.png

394 ms

kotlin.png

kotlin.png

393 ms

android_studio.png

android_studio.png

395 ms

sketch.png

sketch.png

445 ms

xd.png

xd.png

446 ms

zeplin.png

zeplin.png

456 ms

invision.png

invision.png

457 ms

html.png

html.png

455 ms

angular.png

angular.png

504 ms

node.png

node.png

505 ms

php.png

php.png

510 ms

laravel.png

laravel.png

516 ms

codegniter.png

codegniter.png

516 ms

mongdb.png

mongdb.png

516 ms

mysql.png

mysql.png

423 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

66 ms

8At3umuw==

8At3umuw==

53 ms

8At3umuw==

8At3umuw==

60 ms

wC3e6a7

wC3e6a7

60 ms

mssql.png

mssql.png

368 ms

googlecloud.png

googlecloud.png

372 ms

aws.png

aws.png

377 ms

firebasefcm.png

firebasefcm.png

378 ms

firebasecrashlytics.png

firebasecrashlytics.png

374 ms

google_analytics.png

google_analytics.png

420 ms

telr.png

telr.png

357 ms

payfort.png

payfort.png

362 ms

razorpay.png

razorpay.png

369 ms

ccavenue.png

ccavenue.png

369 ms

paytm.png

paytm.png

367 ms

collect

collect

41 ms

minus.svg

minus.svg

371 ms

plus.svg

plus.svg

372 ms

001-online-shop.svg

001-online-shop.svg

374 ms

002-online-learning.svg

002-online-learning.svg

381 ms

003-doctor.svg

003-doctor.svg

371 ms

004-truck.svg

004-truck.svg

368 ms

collect

collect

24 ms

005-social-media.svg

005-social-media.svg

414 ms

ga-audiences

ga-audiences

84 ms

006-house.svg

006-house.svg

368 ms

007-distance.svg

007-distance.svg

369 ms

008-dish.svg

008-dish.svg

370 ms

009-megaphone.svg

009-megaphone.svg

375 ms

round.jpg

round.jpg

432 ms

viju.png

viju.png

364 ms

pic.jpg

pic.jpg

369 ms

message.svg

message.svg

368 ms

calculator.svg

calculator.svg

368 ms

mobile-app.svg

mobile-app.svg

373 ms

whatsapp.png

whatsapp.png

426 ms

project.svg

project.svg

370 ms

flat.svg

flat.svg

377 ms

Accessibility Review

cookee.io accessibility score

78

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

cookee.io best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

cookee.io SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cookee.io 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 Cookee.io 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.

Social Sharing Optimization

cookee.io

Open Graph description is not detected on the main page of Cookee. 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: