Tools & Wizards About Us
frinza.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

frinza.com

Online Cake Store in India | Buy Cakes and Flowers Online | Frinza

Page Load Speed

10.8 sec in total

First Response

23 ms

Resources Loaded

6.7 sec

Page Rendered

4.1 sec

frinza.com screenshot

About Website

Welcome to frinza.com homepage info - get ready to check Frinza best content for India right away, or after learning these important things about frinza.com

Frinza, the best cake shop provides the finest online cake and flower delivery services in 500+ Indian cities. Order online today for same-day or midnight delivery in India of freshly baked cakes.

Visit frinza.com

Key Findings

We analyzed Frinza.com page load time and found that the first response time was 23 ms and then it took 10.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

frinza.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value670 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0.347

32/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

frinza.com

23 ms

frinza.com

530 ms

www.frinza.com

3667 ms

select2.min.css

22 ms

bootstrap.min.css

813 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 92% of them (61 requests) were addressed to the original Frinza.com, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Frinza.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 38.3 kB (2%)

Content Size

2.0 MB

After Optimization

1.9 MB

  • Images
  • JavaScript
  • CSS

In fact, the total size of Frinza.com main page is 2.0 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 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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 web page is already compressed.

Image Optimization

-0%

Potential reduce by 6.9 kB

  • Original 1.8 MB
  • After minification 1.8 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. Frinza images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 24.7 kB

  • Original 129.8 kB
  • After minification 129.8 kB
  • After compression 105.0 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 24.7 kB or 19% of the original size.

CSS Optimization

-38%

Potential reduce by 6.7 kB

  • Original 17.4 kB
  • After minification 15.1 kB
  • After compression 10.7 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. Frinza.com needs all CSS files to be minified and compressed as it can save up to 6.7 kB or 38% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (42%)

Requests Now

60

After Optimization

35

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

frinza.com

frinza.com

23 ms

frinza.com

frinza.com

530 ms

www.frinza.com

www.frinza.com

3667 ms

select2.min.css

select2.min.css

22 ms

bootstrap.min.css

bootstrap.min.css

813 ms

font-awesome.css

font-awesome.css

636 ms

owl.carousel.css

owl.carousel.css

20 ms

owl.theme.css

owl.theme.css

29 ms

jquery.mobile-menu.css

jquery.mobile-menu.css

635 ms

style.css

style.css

1023 ms

blogmate.css

blogmate.css

33 ms

css

css

31 ms

gtm.js

gtm.js

57 ms

Frinza%20Logo%20black.svg

Frinza%20Logo%20black.svg

512 ms

more.png

more.png

1220 ms

a6326271c05e0e25d5a6a4a14b9ace61.jpg

a6326271c05e0e25d5a6a4a14b9ace61.jpg

579 ms

4535398b71574933cd7812a4d9ca4778.jpg

4535398b71574933cd7812a4d9ca4778.jpg

611 ms

b894bf2024ca4ba52e8d2757ce60cbaa.jpg

b894bf2024ca4ba52e8d2757ce60cbaa.jpg

618 ms

8d4b78bfd8cc8dd371420a3a022887e7.jpg

8d4b78bfd8cc8dd371420a3a022887e7.jpg

1234 ms

7003983c13cbfb96932c1cd44816cffa.jpg

7003983c13cbfb96932c1cd44816cffa.jpg

367 ms

9ae32edfafc7c0951176a8e3807905ae.jpg

9ae32edfafc7c0951176a8e3807905ae.jpg

370 ms

3dad5911d39d419841446ad51784c495.jpg

3dad5911d39d419841446ad51784c495.jpg

378 ms

d10bbb7afbdb4588f40a4d032ef4d6cf.jpg

d10bbb7afbdb4588f40a4d032ef4d6cf.jpg

384 ms

48af41f3c102081cb3d22080c9fe7ccd.jpg

48af41f3c102081cb3d22080c9fe7ccd.jpg

390 ms

d33228a17a022de6245747a24ecd1ac2.jpg

d33228a17a022de6245747a24ecd1ac2.jpg

394 ms

d09c79eb6fd63156b8b9112b42cabd02.jpg

d09c79eb6fd63156b8b9112b42cabd02.jpg

401 ms

736f346d8c7e54f3db6a443bf712129b.jpg

736f346d8c7e54f3db6a443bf712129b.jpg

405 ms

9400e9172776db4b60f343df382e0fc5.jpg

9400e9172776db4b60f343df382e0fc5.jpg

412 ms

5db8654ddbb95c8698c626d93eb66519.jpg

5db8654ddbb95c8698c626d93eb66519.jpg

419 ms

ffc4ede4f8b187ad1d6938647c58ef53.jpg

ffc4ede4f8b187ad1d6938647c58ef53.jpg

422 ms

8c2d001d052459db63d6b1d10f16fa04.png

8c2d001d052459db63d6b1d10f16fa04.png

428 ms

64c7e436a2e1de1494e58a133bb6520f.png

64c7e436a2e1de1494e58a133bb6520f.png

431 ms

43af7f0b1ea4d87c3d874742f15c16ef.webp

43af7f0b1ea4d87c3d874742f15c16ef.webp

1082 ms

9bac0a827c151c4e2af1340c97adf6fb.png

9bac0a827c151c4e2af1340c97adf6fb.png

442 ms

f59b171f24d5a5c27f4bdfcd1067728f.png

f59b171f24d5a5c27f4bdfcd1067728f.png

456 ms

e173f3147fa585490bd11ae506ff102c.png

e173f3147fa585490bd11ae506ff102c.png

463 ms

16c6d7c2838d48e0f0b43d148f5bb370.png

16c6d7c2838d48e0f0b43d148f5bb370.png

473 ms

e84fcd139c31ef38c1dc574c91d90ee8.png

e84fcd139c31ef38c1dc574c91d90ee8.png

484 ms

8a38e96a89740e1a5834c7815f3d5dd1.png

8a38e96a89740e1a5834c7815f3d5dd1.png

495 ms

email-decode.min.js

email-decode.min.js

189 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

207 ms

bootstrap.min.js

bootstrap.min.js

766 ms

bootstrap-datepicker.js

bootstrap-datepicker.js

836 ms

common.js

common.js

1060 ms

owl.carousel.min.js

owl.carousel.min.js

1083 ms

lazyload.js

lazyload.js

35 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

38 ms

sweetalert2.min.css

sweetalert2.min.css

703 ms

jquery.mobile-menu.min.js

jquery.mobile-menu.min.js

694 ms

countdown.js

countdown.js

1163 ms

cloud-zoom.js

cloud-zoom.js

1307 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

1220 ms

sweetalert2.min.js

sweetalert2.min.js

1309 ms

select2.min.js

select2.min.js

1537 ms

jquery.lazyload.js

jquery.lazyload.js

1546 ms

custom.js

custom.js

1662 ms

frinza.png

frinza.png

764 ms

bkg_rating.png

bkg_rating.png

774 ms

payment-1.png

payment-1.png

782 ms

payment-2.png

payment-2.png

790 ms

payment-3.png

payment-3.png

806 ms

payment-4.png

payment-4.png

814 ms

Frinza-logo-footer.png

Frinza-logo-footer.png

822 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

156 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

1437 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1709 ms

Accessibility Review

frinza.com accessibility score

85

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

frinza.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

frinza.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frinza.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 Frinza.com main page’s claimed encoding is . 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.

Social Sharing Optimization

frinza.com

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