Tools & Wizards About Us
hollyflower.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

hollyflower.com

Hollyflower | Online Custom Digital Textile Printing in Surat-India

Page Load Speed

1.3 sec in total

First Response

113 ms

Resources Loaded

1.1 sec

Page Rendered

59 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 113 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

hollyflower.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

76/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value15.2 s

1/100

10%

TBT (Total Blocking Time)

Value2,820 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value22.0 s

1/100

10%

Network Requests Diagram

www.hollyflower.com

113 ms

minified.js

40 ms

focus-within-polyfill.js

37 ms

polyfill.min.js

91 ms

thunderbolt-commons.24e46262.bundle.min.js

76 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Hollyflower.com, 30% (13 requests) were made to Static.parastorage.com and 27% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (615 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 542.3 kB (47%)

Content Size

1.2 MB

After Optimization

610.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hollyflower.com main page is 1.2 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 642.6 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 507.3 kB

  • Original 642.6 kB
  • After minification 641.0 kB
  • After compression 135.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. 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 507.3 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 455 B

  • Original 41.3 kB
  • After minification 40.9 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

-8%

Potential reduce by 34.5 kB

  • Original 409.9 kB
  • After minification 409.7 kB
  • After compression 375.4 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 58.8 kB
  • After minification 58.8 kB
  • After compression 58.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. Hollyflower.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

22

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 22 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

113 ms

minified.js

minified.js

40 ms

focus-within-polyfill.js

focus-within-polyfill.js

37 ms

polyfill.min.js

polyfill.min.js

91 ms

thunderbolt-commons.24e46262.bundle.min.js

thunderbolt-commons.24e46262.bundle.min.js

76 ms

main.8752ee81.bundle.min.js

main.8752ee81.bundle.min.js

78 ms

lodash.min.js

lodash.min.js

78 ms

react.production.min.js

react.production.min.js

76 ms

react-dom.production.min.js

react-dom.production.min.js

79 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

68 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

70 ms

d2ce62_2160063ca1ce43f98b3f8fd361a8b6e4~mv2.png

d2ce62_2160063ca1ce43f98b3f8fd361a8b6e4~mv2.png

615 ms

LNqv1h4n1n4

LNqv1h4n1n4

181 ms

bundle.min.js

bundle.min.js

75 ms

d2ce62_66008800bc274de5bebcd94ea8f1fc9d~mv2.jpg

d2ce62_66008800bc274de5bebcd94ea8f1fc9d~mv2.jpg

557 ms

d770fcc6a4694d479c126b8067efc1a3.jpg

d770fcc6a4694d479c126b8067efc1a3.jpg

559 ms

Hollyflower%204.png

Hollyflower%204.png

553 ms

158 ms

376 ms

492 ms

152 ms

489 ms

369 ms

487 ms

486 ms

540 ms

538 ms

548 ms

544 ms

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

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

10 ms

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

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

21 ms

opensans-bold-webfont.woff

opensans-bold-webfont.woff

46 ms

opensans-regular-webfont.woff

opensans-regular-webfont.woff

45 ms

www-player.css

www-player.css

24 ms

www-embed-player.js

www-embed-player.js

58 ms

base.js

base.js

89 ms

ad_status.js

ad_status.js

221 ms

UyQhPWNsNa0oRkd8oSQlA6PkpWpORMW0CLBRczdusu0.js

UyQhPWNsNa0oRkd8oSQlA6PkpWpORMW0CLBRczdusu0.js

159 ms

embed.js

embed.js

67 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

44 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

45 ms

id

id

41 ms

qoe

qoe

9 ms

log_event

log_event

0 ms

Accessibility Review

hollyflower.com accessibility score

89

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

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

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: