Tools & Wizards About Us
hollyflower.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

hollyflower.com

Hollyflower | Online Custom Digital Textile Printing in Surat-India

Page Load Speed

2.5 sec in total

First Response

75 ms

Resources Loaded

2.4 sec

Page Rendered

70 ms

hollyflower.com screenshot

About Website

Click here to check amazing Hollyflower content for India. Otherwise, check out these important facts you probably never knew about hollyflower.com

Hollyflower.com is an online custom digital textile printing factory, sublimation textile printer, and machine company in Surat, Gujarat, India. Hollyflower does Custom Digital Printing on Polyester-C...

Visit hollyflower.com

Key Findings

We analyzed Hollyflower.com page load time and found that the first response time was 75 ms and then it took 2.5 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

hollyflower.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value16.7 s

0/100

10%

TBT (Total Blocking Time)

Value2,440 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value21.8 s

1/100

10%

Network Requests Diagram

www.hollyflower.com

75 ms

minified.js

34 ms

focus-within-polyfill.js

31 ms

polyfill.min.js

1197 ms

thunderbolt-commons.c1d8ed1c.bundle.min.js

24 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Hollyflower.com, 36% (19 requests) were made to Static.parastorage.com and 23% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (63%)

Content Size

1.8 MB

After Optimization

667.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hollyflower.com main page is 1.8 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 712.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 565.1 kB

  • Original 712.5 kB
  • After minification 710.7 kB
  • After compression 147.3 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 565.1 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 1.2 kB

  • Original 40.8 kB
  • After minification 39.6 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. Hollyflower images are well optimized though.

JavaScript Optimization

-34%

Potential reduce by 217.6 kB

  • Original 637.9 kB
  • After minification 637.7 kB
  • After compression 420.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 217.6 kB or 34% of the original size.

CSS Optimization

-85%

Potential reduce by 329.1 kB

  • Original 389.4 kB
  • After minification 388.6 kB
  • After compression 60.2 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. Hollyflower.com needs all CSS files to be minified and compressed as it can save up to 329.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (54%)

Requests Now

28

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.hollyflower.com

www.hollyflower.com

75 ms

minified.js

minified.js

34 ms

focus-within-polyfill.js

focus-within-polyfill.js

31 ms

polyfill.min.js

polyfill.min.js

1197 ms

thunderbolt-commons.c1d8ed1c.bundle.min.js

thunderbolt-commons.c1d8ed1c.bundle.min.js

24 ms

main.4a2d1e74.bundle.min.js

main.4a2d1e74.bundle.min.js

55 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

24 ms

lodash.min.js

lodash.min.js

167 ms

react.production.min.js

react.production.min.js

54 ms

react-dom.production.min.js

react-dom.production.min.js

55 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

55 ms

d2ce62_2160063ca1ce43f98b3f8fd361a8b6e4~mv2.png

d2ce62_2160063ca1ce43f98b3f8fd361a8b6e4~mv2.png

496 ms

d2ce62_66008800bc274de5bebcd94ea8f1fc9d~mv2.jpg

d2ce62_66008800bc274de5bebcd94ea8f1fc9d~mv2.jpg

677 ms

d770fcc6a4694d479c126b8067efc1a3.jpg

d770fcc6a4694d479c126b8067efc1a3.jpg

769 ms

Hollyflower%204.png

Hollyflower%204.png

787 ms

LNqv1h4n1n4

LNqv1h4n1n4

195 ms

bundle.min.js

bundle.min.js

58 ms

03805817-4611-4dbc-8c65-0f73031c3973.woff

03805817-4611-4dbc-8c65-0f73031c3973.woff

38 ms

cca525a8-ad89-43ae-aced-bcb49fb271dc.woff

cca525a8-ad89-43ae-aced-bcb49fb271dc.woff

39 ms

opensans-bold-webfont.woff

opensans-bold-webfont.woff

39 ms

opensans-regular-webfont.woff

opensans-regular-webfont.woff

39 ms

255 ms

251 ms

252 ms

250 ms

250 ms

250 ms

397 ms

393 ms

393 ms

393 ms

390 ms

390 ms

www-player.css

www-player.css

8 ms

www-embed-player.js

www-embed-player.js

30 ms

base.js

base.js

54 ms

ad_status.js

ad_status.js

189 ms

Kwl4UTqRlZdwo60dxzGVsyg_CEkasAzkebPPx38d0Do.js

Kwl4UTqRlZdwo60dxzGVsyg_CEkasAzkebPPx38d0Do.js

132 ms

embed.js

embed.js

52 ms

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

54 ms

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

57 ms

Create

Create

104 ms

id

id

11 ms

GenerateIT

GenerateIT

12 ms

qoe

qoe

8 ms

log_event

log_event

1 ms

deprecation-en.v5.html

deprecation-en.v5.html

5 ms

bolt-performance

bolt-performance

19 ms

deprecation-style.v5.css

deprecation-style.v5.css

5 ms

right-arrow.svg

right-arrow.svg

13 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

4 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

8 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

5 ms

Accessibility Review

hollyflower.com accessibility score

90

Accessibility Issues

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

Buttons do not have an accessible name

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

Heading elements are not in a sequentially-descending order

Best Practices

hollyflower.com best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

hollyflower.com SEO score

100

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

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

hollyflower.com

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