Access daylilyfloral.com. Grand Rapids Florist | Flower Delivery in Grand Rapids, MI by Daylily Floral Cascade

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

daylilyfloral.com

42 ms

www.daylilyfloral.com

334 ms

css2

42 ms

style.min.css

184 ms

ExitIntent.min.css

204 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 6% of them (5 requests) were addressed to the original Daylilyfloral.com, 62% (50 requests) were made to Res.cloudinary.com and 26% (21 requests) were made to Hana-cdn-g9fcbgbya0azddab.a01.azurefd.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Res.cloudinary.com.

Content Size

7.8 MB

After Optimization

7.6 MB

In fact, the total size of Daylilyfloral.com main page is 7.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. Only a small number of websites need less resources to load. Images take 7.4 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 109.6 kB

Original 124.1 kB
After minification 86.8 kB
After compression 14.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 37.3 kB, which is 30% 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 109.6 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 29.6 kB

Original 7.4 MB
After minification 7.3 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. Daylily Floral images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 40.7 kB

Original 252.9 kB
After minification 252.9 kB
After compression 212.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 40.7 kB or 16% of the original size.

CSS Optimization

-25%

Potential reduce by 22.8 kB

Original 89.9 kB
After minification 89.9 kB
After compression 67.1 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. Daylilyfloral.com needs all CSS files to be minified and compressed as it can save up to 22.8 kB or 25% of the original size.

Requests Now

After Optimization

The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Daylily Floral. 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 from 7 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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 keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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

EN
Language Claimed

EN
Encoding

UTF-8

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

daylilyfloral.com

Open Graph data is detected on the main page of Daylily Floral. 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

Grand Rapids Florist | Flower Delivery in Grand Rapids, MI by Daylily Floral Cascade

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

daylilyfloral.com

www.daylilyfloral.com

css2

style.min.css

ExitIntent.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

daylilyfloral.com

www.daylilyfloral.com

css2

style.min.css

ExitIntent.min.css

toastr.min.css

labs.min.css

masonry.min.css

BannerModel.min.css

js

jquery-3.1.1.min.js

jquery-ui.min.js

bootstrap.min.js

handlebars-v4.0.5.min.js

handlebars-custom.min.js

jquery.elevatezoom.min.js

fancybox.pack.min.js

owl.carousel.min.js

sweetalert.min.js

lazysizes.min.js

cloudinary-core-shrinkwrap.min.js

toastr.min.js

jquery.exitintent.min.js

Global.min.js

_CommonHome.min.js

rqv1je0zkcwuczif598w.png

prev.png

congrats.jpg

hyysz17lm33jkdkogw4n.jpg

qc2vmkq6aaeysspuwb6b.jpg

fgitpkgt2e8rsgk6bicl.jpg

pink_flowers_qxk0xs.jpg

izisczdjvdgwr0f1m0ud.jpg

d7t0aaksqncbhk3ranmm.jpg

cltwgp4cytnyfsygaycf.jpg

hhn5gffl48gfgp8d7fhz.jpg

kgsp0uzmc0xhp600sdai.jpg

hds7dnmxgstdlhbcdjxs.jpg

gckmtifb8jpw5ubvhbcl.jpg

dyelch1lyy6gu1vtmdmc.jpg

j3bajodbionw4uoxfdzl.jpg

d3owp6qujdnl6jmi0q4l.jpg

fdzq2bma31cw0f1kyywa.jpg