Access cakestory.in.

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value18.9 s

0/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value6,710 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value17.0 s

4/100

10%

cakestory.in

2090 ms

foundation.min.css

49 ms

font-awesome.min.css

118 ms

animate.min.css

155 ms

owl.carousel.min.css

918 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Cakestory.in, 55% (34 requests) were made to S3-ap-southeast-1.amazonaws.com and 15% (9 requests) were made to Assets.limetray.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Cakestory.in.

Content Size

1.9 MB

After Optimization

1.8 MB

In fact, the total size of Cakestory.in main page is 1.9 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 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 80.4 kB

Original 96.9 kB
After minification 85.2 kB
After compression 16.5 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.7 kB, which is 12% 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 80.4 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 12.4 kB

Original 1.7 MB
After minification 1.7 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. Cakestory images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 39.4 kB

Original 73.1 kB
After minification 73.1 kB
After compression 33.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 39.4 kB or 54% of the original size.

CSS Optimization

-71%

Potential reduce by 11.3 kB

Original 16.0 kB
After minification 15.2 kB
After compression 4.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. Cakestory.in needs all CSS files to be minified and compressed as it can save up to 11.3 kB or 71% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

ARIA input fields do not have accessible names

These are opportunities to improve the legibility of your content.

High

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

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.

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

Links do not have descriptive text

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

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

N/A
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cakestory.in 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), while the claimed language is English. Our system also found out that Cakestory.in 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

cakestory.in

Open Graph data is detected on the main page of Cakestory. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

cakestory.in

foundation.min.css

font-awesome.min.css

animate.min.css

owl.carousel.min.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

cakestory.in

foundation.min.css

font-awesome.min.css

animate.min.css

owl.carousel.min.css

main.min.css

header.min.css

tc.min.css

jquery.min.js

modernizr.min.js

foundation.min.js

js

parallax-script.js

slick.css

slick.min.js

smoothscroll.js

home.min.css

footer.min.css

owl.carousel.min.js

jquery.lazyload.js

analytics.js

gtm.js

fbevents.js

whatsapp-honey.png

1501919685_CakeStoryLogo3.png

cake-story-a12.jpg

cake-story-a16.jpg

cake-story-a14.jpg

cake-story-a15.jpg

cake-story-icon6.png

cake-story-icon5.png

cake-story-icon4.png

cake-story-icon3.png

cake-story-icon2.png

cake-story-icon1.png

cake-story-z6.jpg

cake-story-featured-brownies.jpg

cake-story-featured-muffins.jpg

cake-story-featured-cookie.jpg

cake-story-featured-tea-cake.jpg

cake-story-featured-desserts.jpg

cake-story-featured-pie.jpg

cake-story-featured-savory.jpg

js