Tools & Wizards About Us
daylilyworld.com screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

daylilyworld.com

David Kirchhoff and Mort Morss at Daylily world

Page Load Speed

1.7 sec in total

First Response

248 ms

Resources Loaded

1.2 sec

Page Rendered

279 ms

daylilyworld.com screenshot

About Website

Welcome to daylilyworld.com homepage info - get ready to check Daylily World best content right away, or after learning these important things about daylilyworld.com

Daylily World is one of the top daylily businesses in the world. David Kirchhoff and Mort Morss at Daylily World have been selling beautiful Daylilies Since 1971.

Visit daylilyworld.com

Key Findings

We analyzed Daylilyworld.com page load time and found that the first response time was 248 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

daylilyworld.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

18/100

25%

SI (Speed Index)

Value5.3 s

59/100

10%

TBT (Total Blocking Time)

Value510 ms

57/100

30%

CLS (Cumulative Layout Shift)

Value0.035

100/100

15%

TTI (Time to Interactive)

Value8.1 s

42/100

10%

Network Requests Diagram

daylilyworld.com

248 ms

129 ms

package-sf.css

140 ms

package-sf.js

293 ms

StorefrontStyle_102.css

151 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that all of those requests were addressed to Daylilyworld.com and no external sources were called. The less responsive or slowest element that took the longest time to load (487 ms) belongs to the original domain Daylilyworld.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 533.9 kB (53%)

Content Size

1.0 MB

After Optimization

466.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Daylilyworld.com main page is 1.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. 35% of websites need less resources to load. Javascripts take 426.9 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 35.9 kB

  • Original 43.9 kB
  • After minification 37.3 kB
  • After compression 8.0 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 6.6 kB, which is 15% 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 35.9 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 609 B

  • Original 276.0 kB
  • After minification 275.4 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. Daylily World images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 289.4 kB

  • Original 426.9 kB
  • After minification 426.0 kB
  • After compression 137.5 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 289.4 kB or 68% of the original size.

CSS Optimization

-82%

Potential reduce by 208.0 kB

  • Original 253.7 kB
  • After minification 222.2 kB
  • After compression 45.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. Daylilyworld.com needs all CSS files to be minified and compressed as it can save up to 208.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (62%)

Requests Now

66

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

daylilyworld.com

daylilyworld.com

248 ms

129 ms

package-sf.css

package-sf.css

140 ms

package-sf.js

package-sf.js

293 ms

StorefrontStyle_102.css

StorefrontStyle_102.css

151 ms

style-ie.css

style-ie.css

52 ms

en-US.js

en-US.js

65 ms

USD.js

USD.js

73 ms

string.js

string.js

70 ms

browser.js

browser.js

82 ms

scope.js

scope.js

105 ms

json.js

json.js

107 ms

base64.js

base64.js

105 ms

inject-sec-token.js

inject-sec-token.js

109 ms

cookie.js

cookie.js

106 ms

storage.js

storage.js

120 ms

button.js

button.js

106 ms

draggable.js

draggable.js

113 ms

resizable.js

resizable.js

123 ms

$pub.js

$pub.js

118 ms

class.js

class.js

119 ms

mime.js

mime.js

142 ms

$dict.js

$dict.js

144 ms

core.js

core.js

144 ms

support.js

support.js

149 ms

$tmpl.js

$tmpl.js

151 ms

load.js

load.js

157 ms

touch.js

touch.js

178 ms

version.js

version.js

180 ms

validate.js

validate.js

183 ms

de_epages.js

de_epages.js

190 ms

bgr_layout.png

bgr_layout.png

180 ms

test34212add.jpg

test34212add.jpg

223 ms

ico_l_basket.png

ico_l_basket.png

203 ms

ico_s_search.png

ico_s_search.png

204 ms

cropped..jpg

cropped..jpg

294 ms

morts_2016_strip2.jpg

morts_2016_strip2.jpg

487 ms

Find-us-on-Facebook.png

Find-us-on-Facebook.png

226 ms

AuthorizeNetLogo.gif

AuthorizeNetLogo.gif

247 ms

ico_m_visa.gif

ico_m_visa.gif

248 ms

ico_m_mastercard.gif

ico_m_mastercard.gif

269 ms

ico_m_amex.gif

ico_m_amex.gif

268 ms

ico_m_diners.gif

ico_m_diners.gif

281 ms

ico_m_jcb.gif

ico_m_jcb.gif

279 ms

ico_m_discover.gif

ico_m_discover.gif

302 ms

suggest.js

suggest.js

280 ms

megamenu.js

megamenu.js

284 ms

$ready.js

$ready.js

285 ms

ico_m_paypal.gif

ico_m_paypal.gif

286 ms

applePay.gif

applePay.gif

308 ms

cookiemessage.js

cookiemessage.js

310 ms

energylabel.js

energylabel.js

313 ms

utf8.js

utf8.js

312 ms

e_check.gif

e_check.gif

298 ms

logo.jpg

logo.jpg

322 ms

bgr_top_floatin.png

bgr_top_floatin.png

323 ms

bgr_top.png

bgr_top.png

327 ms

bgr_content.png

bgr_content.png

311 ms

dict.en.json

dict.en.json

308 ms

img_content_separatorline.png

img_content_separatorline.png

333 ms

ico_s_printer.png

ico_s_printer.png

333 ms

bgr_footer_floatin.png

bgr_footer_floatin.png

333 ms

bgr_footer.png

bgr_footer.png

342 ms

dictionary.en.json

dictionary.en.json

146 ms

masonry.js

masonry.js

166 ms

facebook.js

facebook.js

169 ms

simpledialog.js

simpledialog.js

154 ms

Accessibility Review

daylilyworld.com accessibility score

76

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

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

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

daylilyworld.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

daylilyworld.com SEO score

79

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

High

Image elements do not have [alt] attributes

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

    EN

  • Encoding

    UTF-8

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

daylilyworld.com

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