Tools & Wizards About Us
cookabox.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

cookabox.com

Cook a Box | Coming Soon

Page Load Speed

3.5 sec in total

First Response

274 ms

Resources Loaded

2.5 sec

Page Rendered

731 ms

cookabox.com screenshot

About Website

Click here to check amazing Cook A Box content for United Arab Emirates. Otherwise, check out these important facts you probably never knew about cookabox.com

Visit cookabox.com

Key Findings

We analyzed Cookabox.com page load time and found that the first response time was 274 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster. This domain responded with an error, which can significantly jeopardize Cookabox.com rating and web reputation

Performance Metrics

cookabox.com performance score

0

Network Requests Diagram

cookabox.com

274 ms

css

34 ms

font-awesome.min.css

231 ms

bootstrap.css

368 ms

custom.css

279 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 68% of them (47 requests) were addressed to the original Cookabox.com, 4% (3 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Cookabox.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 668.2 kB (13%)

Content Size

5.1 MB

After Optimization

4.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cookabox.com main page is 5.1 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. 70% of websites need less resources to load. Images take 4.3 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 47.0 kB

  • Original 56.2 kB
  • After minification 45.3 kB
  • After compression 9.2 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 11.0 kB, which is 20% 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 47.0 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 88.7 kB

  • Original 4.3 MB
  • After minification 4.2 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. Cook A Box images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 229.3 kB

  • Original 359.3 kB
  • After minification 352.2 kB
  • After compression 130.1 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 229.3 kB or 64% of the original size.

CSS Optimization

-84%

Potential reduce by 303.2 kB

  • Original 360.0 kB
  • After minification 322.6 kB
  • After compression 56.8 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. Cookabox.com needs all CSS files to be minified and compressed as it can save up to 303.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (39%)

Requests Now

57

After Optimization

35

  • Images
  • JavaScript
  • CSS

The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cook A Box. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

cookabox.com

cookabox.com

274 ms

css

css

34 ms

font-awesome.min.css

font-awesome.min.css

231 ms

bootstrap.css

bootstrap.css

368 ms

custom.css

custom.css

279 ms

css

css

83 ms

widgets.js

widgets.js

83 ms

jquery.min.js

jquery.min.js

81 ms

jquery.js

jquery.js

473 ms

initcarousel-1.css

initcarousel-1.css

263 ms

jquery.fancybox.css

jquery.fancybox.css

204 ms

ReferenceCSS.css

ReferenceCSS.css

438 ms

font-awesome.min.css

font-awesome.min.css

34 ms

timeline.fe2df323b0284f547735e29f610f34bf.js

timeline.fe2df323b0284f547735e29f610f34bf.js

126 ms

WebResource.axd

WebResource.axd

190 ms

mc-validate.js

mc-validate.js

188 ms

jquery.min.js

jquery.min.js

31 ms

jquery-latest.min.js

jquery-latest.min.js

4 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

212 ms

amazingcarousel.js

amazingcarousel.js

339 ms

initcarousel-1.js

initcarousel-1.js

307 ms

bootstrap.min.js

bootstrap.min.js

317 ms

css

css

19 ms

style.css

style.css

59 ms

fbds.js

fbds.js

40 ms

default.jsp

default.jsp

545 ms

logo-footer.png

logo-footer.png

260 ms

bg.png

bg.png

80 ms

logo.png

logo.png

218 ms

106.jpg

106.jpg

219 ms

92.jpg

92.jpg

216 ms

111.jpg

111.jpg

218 ms

91.jpg

91.jpg

506 ms

95.jpg

95.jpg

254 ms

105.jpg

105.jpg

502 ms

112.jpg

112.jpg

505 ms

99.jpg

99.jpg

258 ms

103.jpg

103.jpg

661 ms

hworks-dish.png

hworks-dish.png

503 ms

forbes_middle_east_logo.png

forbes_middle_east_logo.png

502 ms

national.jpg

national.jpg

585 ms

ahlan.jpg

ahlan.jpg

535 ms

goodhousekeeping.gif

goodhousekeeping.gif

626 ms

banner4.jpg

banner4.jpg

671 ms

hworks-bg.png

hworks-bg.png

1778 ms

icon_choose.png

icon_choose.png

567 ms

icon_shop.png

icon_shop.png

616 ms

icon_recipies.png

icon_recipies.png

628 ms

icon_deliver.png

icon_deliver.png

659 ms

joinus-bg.png

joinus-bg.png

1653 ms

184 ms

Museo-300.otf

Museo-300.otf

629 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

5 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

651 ms

Museo-700.otf

Museo-700.otf

669 ms

analytics.js

analytics.js

115 ms

lightbox-next.png

lightbox-next.png

568 ms

lightbox-prev.png

lightbox-prev.png

568 ms

lightbox-close.png

lightbox-close.png

569 ms

arrows-32-32-2.png

arrows-32-32-2.png

577 ms

bullet-16-16-0.png

bullet-16-16-0.png

589 ms

collect

collect

19 ms

widget_v2.134.js

widget_v2.134.js

34 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

250 ms

collect

collect

277 ms

ga-audiences

ga-audiences

35 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

484 ms

aL63HcygAAVYuCCsAAA==

aL63HcygAAVYuCCsAAA==

10 ms

21 ms

SEO Factors

cookabox.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cookabox.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Cookabox.com 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

cookabox.com

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