Tools & Wizards About Us
daylily.ws screenshot

Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

daylily.ws

Welcome to Riverbend Daylily Garden

Page Load Speed

1.3 sec in total

First Response

205 ms

Resources Loaded

931 ms

Page Rendered

211 ms

daylily.ws screenshot

About Website

Click here to check amazing Daylily content. Otherwise, check out these important facts you probably never knew about daylily.ws

Welcome to the July 2017 Riverbend Daylily Garden Website. We specialize in unique tetraploid daylilies. Patterns and Teeth. We are located on the web at www.daylily.ws, www.sandyholmes.com, www.river...

Visit daylily.ws

Key Findings

We analyzed Daylily.ws page load time and found that the first response time was 205 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 25% of websites can load faster.

Performance Metrics

daylily.ws performance score

0

Network Requests Diagram

daylily.ws

205 ms

196 ms

corporatestyle.css

220 ms

javascripts.js

112 ms

pop-closeup.js

139 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Daylily.ws, 68% (19 requests) were made to Daylilytrader.com and 11% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (360 ms) relates to the external source Daylilytrader.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 362.2 kB (66%)

Content Size

550.8 kB

After Optimization

188.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Daylily.ws main page is 550.8 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. 60% of websites need less resources to load. CSS take 253.7 kB which makes up the majority of the site volume.

HTML Optimization

-48%

Potential reduce by 484 B

  • Original 998 B
  • After minification 949 B
  • After compression 514 B

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 484 B or 48% of the original size.

Image Optimization

-9%

Potential reduce by 6.3 kB

  • Original 74.1 kB
  • After minification 67.8 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 images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 144.9 kB

  • Original 222.0 kB
  • After minification 219.6 kB
  • After compression 77.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 144.9 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 210.5 kB

  • Original 253.7 kB
  • After minification 250.8 kB
  • After compression 43.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. Daylily.ws needs all CSS files to be minified and compressed as it can save up to 210.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (38%)

Requests Now

24

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

daylily.ws

daylily.ws

205 ms

196 ms

corporatestyle.css

corporatestyle.css

220 ms

javascripts.js

javascripts.js

112 ms

pop-closeup.js

pop-closeup.js

139 ms

header.js

header.js

142 ms

menu.js

menu.js

212 ms

home-image.js

home-image.js

154 ms

copyright.js

copyright.js

106 ms

copyright-allwebco.js

copyright-allwebco.js

146 ms

header_image.jpg

header_image.jpg

106 ms

bar.gif

bar.gif

105 ms

spacer.gif

spacer.gif

94 ms

background-menu.gif

background-menu.gif

125 ms

menu.gif

menu.gif

125 ms

background.jpg

background.jpg

179 ms

home-1.jpg

home-1.jpg

360 ms

background_picture_end.jpg

background_picture_end.jpg

287 ms

bar-footer.jpg

bar-footer.jpg

285 ms

background-bottom-shade.gif

background-bottom-shade.gif

286 ms

lVV_Bm-K-I0

lVV_Bm-K-I0

76 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

39 ms

www-embed-player.js

www-embed-player.js

58 ms

base.js

base.js

77 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

36 ms

ad_status.js

ad_status.js

38 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

28 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

29 ms

Accessibility Review

daylily.ws accessibility score

33

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

<frame> or <iframe> elements do not have a title

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

daylily.ws best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

daylily.ws SEO score

73

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Daylily.ws can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Daylily.ws 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

daylily.ws

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