Tools & Wizards About Us
gracelandgardens.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

gracelandgardens.com

Graceland Gardens

Page Load Speed

1.6 sec in total

First Response

160 ms

Resources Loaded

1.3 sec

Page Rendered

179 ms

gracelandgardens.com screenshot

About Website

Welcome to gracelandgardens.com homepage info - get ready to check Graceland Gardens best content right away, or after learning these important things about gracelandgardens.com

Larry Grace' s daylily introduction website.

Visit gracelandgardens.com

Key Findings

We analyzed Gracelandgardens.com page load time and found that the first response time was 160 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

gracelandgardens.com performance score

0

Network Requests Diagram

gracelandgardens.com

160 ms

259 ms

corporatestyle.css

172 ms

javascripts.js

112 ms

pop-closeup.js

136 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Gracelandgardens.com, 95% (20 requests) were made to Daylilytrader.com. The less responsive or slowest element that took the longest time to load (693 ms) relates to the external source Daylilytrader.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 20.4 kB (10%)

Content Size

210.4 kB

After Optimization

189.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gracelandgardens.com main page is 210.4 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. Only 10% of websites need less resources to load. Images take 191.3 kB which makes up the majority of the site volume.

HTML Optimization

-44%

Potential reduce by 252 B

  • Original 567 B
  • After minification 519 B
  • After compression 315 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 252 B or 44% of the original size.

Image Optimization

-3%

Potential reduce by 5.6 kB

  • Original 191.3 kB
  • After minification 185.7 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. Graceland Gardens images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 6.9 kB

  • Original 9.3 kB
  • After minification 6.4 kB
  • After compression 2.4 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 6.9 kB or 74% of the original size.

CSS Optimization

-84%

Potential reduce by 7.7 kB

  • Original 9.3 kB
  • After minification 6.5 kB
  • After compression 1.5 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. Gracelandgardens.com needs all CSS files to be minified and compressed as it can save up to 7.7 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (25%)

Requests Now

20

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gracelandgardens.com

gracelandgardens.com

160 ms

259 ms

corporatestyle.css

corporatestyle.css

172 ms

javascripts.js

javascripts.js

112 ms

pop-closeup.js

pop-closeup.js

136 ms

header.js

header.js

155 ms

menu.js

menu.js

226 ms

copyright.js

copyright.js

98 ms

copyright-allwebco.js

copyright-allwebco.js

115 ms

header_image.jpg

header_image.jpg

64 ms

bar.gif

bar.gif

82 ms

spacer.gif

spacer.gif

76 ms

background-menu.gif

background-menu.gif

71 ms

larryandcindy.jpg

larryandcindy.jpg

603 ms

Briar_Patch2b.jpg

Briar_Patch2b.jpg

123 ms

CONTACT.gif

CONTACT.gif

120 ms

menu.gif

menu.gif

87 ms

background.jpg

background.jpg

174 ms

background-picture-end.jpg

background-picture-end.jpg

693 ms

bar-footer.jpg

bar-footer.jpg

132 ms

background-bottom-shade.gif

background-bottom-shade.gif

145 ms

SEO Factors

gracelandgardens.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gracelandgardens.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Gracelandgardens.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

gracelandgardens.com

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