Tools & Wizards About Us
daylilyblog.com screenshot

Report Summary

  • 75

    Performance

    Renders faster than
    83% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

daylilyblog.com

The Daylily Lovers Blog - Presented by Day-lily.com and Spring Hill Nurseries

Page Load Speed

3.7 sec in total

First Response

158 ms

Resources Loaded

3 sec

Page Rendered

538 ms

daylilyblog.com screenshot

About Website

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

Welcome to the best destination for all your Daylily flower needs! This blog is brought to you by the experts at Spring Hill Nurseries and IrisLovers.com, the

Visit daylilyblog.com

Key Findings

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

Performance Metrics

daylilyblog.com performance score

75

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

55/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value5.1 s

75/100

10%

Network Requests Diagram

daylilyblog.com

158 ms

www.daylilyblog.com

523 ms

wp-emoji-release.min.js

156 ms

addtoany.min.css

179 ms

jquery.js

299 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 38% of them (12 requests) were addressed to the original Daylilyblog.com, 16% (5 requests) were made to Youtube.com and 16% (5 requests) were made to Springhillnursery.com. The less responsive or slowest element that took the longest time to load (578 ms) relates to the external source Springhillnursery.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 135.5 kB (30%)

Content Size

451.7 kB

After Optimization

316.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Daylilyblog.com main page is 451.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% 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. Javascripts take 237.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 123.3 kB

  • Original 153.9 kB
  • After minification 152.4 kB
  • After compression 30.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. 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 123.3 kB or 80% of the original size.

Image Optimization

-29%

Potential reduce by 322 B

  • Original 1.1 kB
  • After minification 806 B

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. Obviously, Daylily Blog needs image optimization as it can save up to 322 B or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-5%

Potential reduce by 11.8 kB

  • Original 237.5 kB
  • After minification 237.5 kB
  • After compression 225.7 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 25 B

  • Original 59.2 kB
  • After minification 59.2 kB
  • After compression 59.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. Daylilyblog.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 8 (44%)

Requests Now

18

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

daylilyblog.com

daylilyblog.com

158 ms

www.daylilyblog.com

www.daylilyblog.com

523 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

156 ms

addtoany.min.css

addtoany.min.css

179 ms

jquery.js

jquery.js

299 ms

jquery-migrate.min.js

jquery-migrate.min.js

183 ms

wp-embed.min.js

wp-embed.min.js

96 ms

76218.jpg

76218.jpg

384 ms

36_165_popup.jpg

36_165_popup.jpg

379 ms

DaylilyLoversLogo.jpg

DaylilyLoversLogo.jpg

384 ms

comment-gray.png

comment-gray.png

378 ms

email-gray.png

email-gray.png

374 ms

rss-gray.png

rss-gray.png

375 ms

inputbackgr.gif

inputbackgr.gif

375 ms

49_178_popup.jpg

49_178_popup.jpg

378 ms

70_203_popup.jpg

70_203_popup.jpg

379 ms

page.js

page.js

360 ms

1HEZU-SNEtA

1HEZU-SNEtA

131 ms

75641.jpg

75641.jpg

505 ms

vhLR39W9Nuk

vhLR39W9Nuk

159 ms

videos-video-26.jpg

videos-video-26.jpg

504 ms

75908.jpg

75908.jpg

578 ms

74568.jpg

74568.jpg

577 ms

17004.jpg

17004.jpg

500 ms

76218.jpg

76218.jpg

25 ms

sm.25.html

sm.25.html

34 ms

eso.BRQnzO8v.js

eso.BRQnzO8v.js

41 ms

76218.jpg

76218.jpg

14 ms

icons.38.svg.js

icons.38.svg.js

29 ms

www-player.css

www-player.css

8 ms

www-embed-player.js

www-embed-player.js

31 ms

base.js

base.js

64 ms

Accessibility Review

daylilyblog.com accessibility score

82

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

Form elements do not have associated labels

High

<object> elements do not have alternate text

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

daylilyblog.com SEO score

71

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

Document uses plugins

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

daylilyblog.com

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