Tools & Wizards About Us
daylily.net screenshot

Report Summary

  • 95

    Performance

    Renders faster than
    93% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

daylily.net

Daylilies of North Carolina

Page Load Speed

23.8 sec in total

First Response

460 ms

Resources Loaded

7.4 sec

Page Rendered

15.9 sec

daylily.net screenshot

About Website

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

Daylilies of North Carolina is the hybriding garden of Bobby Baxter that is at the forefront of the advanced development of polymerous daylilies. Located in Wake Forest, NC.

Visit daylily.net

Key Findings

We analyzed Daylily.net page load time and found that the first response time was 460 ms and then it took 23.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

daylily.net performance score

95

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

76/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

93/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.0 s

95/100

10%

Network Requests Diagram

daylily.net

460 ms

index.asp

532 ms

p7EPM02.css

267 ms

p7EPMscripts.js

230 ms

p7iqGlobal_basic.css

285 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 86% of them (42 requests) were addressed to the original Daylily.net, 4% (2 requests) were made to Facebook.com and 4% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (4.4 sec) relates to the external source Images.paypal.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 105.2 kB (3%)

Content Size

3.1 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Daylily.net main page is 3.1 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. 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. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 19.5 kB

  • Original 26.5 kB
  • After minification 24.6 kB
  • After compression 7.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. 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 19.5 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 64.9 kB

  • Original 3.1 MB
  • After minification 3.0 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 images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 13.3 kB

  • Original 18.9 kB
  • After minification 15.7 kB
  • After compression 5.6 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 13.3 kB or 70% of the original size.

CSS Optimization

-77%

Potential reduce by 7.4 kB

  • Original 9.6 kB
  • After minification 5.8 kB
  • After compression 2.2 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.net needs all CSS files to be minified and compressed as it can save up to 7.4 kB or 77% of the original size.

Requests Breakdown

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

Requests Now

47

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 47 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 4 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

daylily.net

daylily.net

460 ms

index.asp

index.asp

532 ms

p7EPM02.css

p7EPM02.css

267 ms

p7EPMscripts.js

p7EPMscripts.js

230 ms

p7iqGlobal_basic.css

p7iqGlobal_basic.css

285 ms

p7iq25.css

p7iq25.css

284 ms

p7popmenu.js

p7popmenu.js

521 ms

p7EPM04.css

p7EPM04.css

311 ms

jspw3x.js

jspw3x.js

521 ms

p7pmh29.css

p7pmh29.css

65 ms

x-click-but6.gif

x-click-but6.gif

4447 ms

p7iq_masthead.jpg

p7iq_masthead.jpg

318 ms

daylilies_of_nc_banner.jpg

daylilies_of_nc_banner.jpg

808 ms

Petal_Power-Secret_Agent_Babe-200.jpg

Petal_Power-Secret_Agent_Babe-200.jpg

809 ms

redefining_genetics-webpage-200.jpg

redefining_genetics-webpage-200.jpg

807 ms

2013_blooms_and_ale_festival-640.jpg

2013_blooms_and_ale_festival-640.jpg

806 ms

runner_dude-200.jpg

runner_dude-200.jpg

804 ms

barefoot_and_pregnant-200.jpg

barefoot_and_pregnant-200.jpg

376 ms

IMG_1253-200.jpg

IMG_1253-200.jpg

748 ms

buttercup_kiss-200.jpg

buttercup_kiss-200.jpg

786 ms

walk_on_the_beach-200.jpg

walk_on_the_beach-200.jpg

1065 ms

medoc_mountain-a-200a.jpg

medoc_mountain-a-200a.jpg

1090 ms

alien_skin-200.jpg

alien_skin-200.jpg

1070 ms

run_time_error-200.jpg

run_time_error-200.jpg

1069 ms

x-tra_baggage-200a.jpg

x-tra_baggage-200a.jpg

1070 ms

good_girls_do-baxter-200.jpg

good_girls_do-baxter-200.jpg

1070 ms

Fractured_Symmetry-Baxter-200.jpg

Fractured_Symmetry-Baxter-200.jpg

1070 ms

carolina_starfish-e200.jpg

carolina_starfish-e200.jpg

1028 ms

moments_that_linger-c200.jpg

moments_that_linger-c200.jpg

1027 ms

time_to_play-200.jpg

time_to_play-200.jpg

1112 ms

runner_chick-200.jpg

runner_chick-200.jpg

1113 ms

swim_bike_run-200.jpg

swim_bike_run-200.jpg

1110 ms

hugh_nourse-200.jpg

hugh_nourse-200.jpg

1110 ms

reaching_new_heights-clump200.jpg

reaching_new_heights-clump200.jpg

1111 ms

in_celebration_of_life-b200.jpg

in_celebration_of_life-b200.jpg

1129 ms

status_update-200.jpg

status_update-200.jpg

1130 ms

time_and_dimension-f200.jpg

time_and_dimension-f200.jpg

1340 ms

courage_and_determination-a200.jpg

courage_and_determination-a200.jpg

1341 ms

p7iq_navbg.jpg

p7iq_navbg.jpg

1241 ms

pmiQ_subs.jpg

pmiQ_subs.jpg

1190 ms

p7iq_2col940.jpg

p7iq_2col940.jpg

1190 ms

p7iq_2col940Top.jpg

p7iq_2col940Top.jpg

1190 ms

all.js

all.js

349 ms

p7iq_2col940Bottom.jpg

p7iq_2col940Bottom.jpg

207 ms

355 ms

0sTQzbapM8j.js

0sTQzbapM8j.js

937 ms

0sTQzbapM8j.js

0sTQzbapM8j.js

994 ms

like.php

like.php

539 ms

lH1ibRl5GKq.png

lH1ibRl5GKq.png

98 ms

Accessibility Review

daylily.net accessibility score

64

Accessibility Issues

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

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

daylily.net 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

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

daylily.net SEO score

67

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

Image elements do not have [alt] attributes

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

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: