Tools & Wizards About Us
hort.net screenshot

Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

hort.net

hort.net -- trade plants, info, and seeds while making gardening friends online!

Page Load Speed

1.7 sec in total

First Response

340 ms

Resources Loaded

1.2 sec

Page Rendered

168 ms

hort.net screenshot

About Website

Visit hort.net now to see the best up-to-date Hort content for United States and also check out these interesting facts you probably never knew about hort.net

A regularly updated collection of full-color photographs, mailing lists, plant profiles, and links covering perennials, annuals, woody plants, and all types of plant material and related topics.

Visit hort.net

Key Findings

We analyzed Hort.net page load time and found that the first response time was 340 ms and then it took 1.3 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

hort.net performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

89/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.5 s

92/100

10%

Network Requests Diagram

hort.net

340 ms

www.hort.net

432 ms

hort.css

41 ms

gplus-16.png

94 ms

250x109xhortnet-logo-C.jpg.pagespeed.ic.N3p5m5ctRx.jpg

91 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 59% of them (24 requests) were addressed to the original Hort.net, 17% (7 requests) were made to Apis.google.com and 7% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (432 ms) belongs to the original domain Hort.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 26.7 kB (23%)

Content Size

118.8 kB

After Optimization

92.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hort.net main page is 118.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. 30% of websites need less resources to load. Images take 69.6 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 15.5 kB

  • Original 20.5 kB
  • After minification 20.5 kB
  • After compression 5.1 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 15.5 kB or 75% of the original size.

Image Optimization

-6%

Potential reduce by 4.0 kB

  • Original 69.6 kB
  • After minification 65.6 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. Hort images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 4.7 kB

  • Original 25.1 kB
  • After minification 25.1 kB
  • After compression 20.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 4.7 kB or 19% of the original size.

CSS Optimization

-73%

Potential reduce by 2.6 kB

  • Original 3.6 kB
  • After minification 2.8 kB
  • After compression 960 B

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. Hort.net needs all CSS files to be minified and compressed as it can save up to 2.6 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (47%)

Requests Now

38

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hort.net

hort.net

340 ms

www.hort.net

www.hort.net

432 ms

hort.css

hort.css

41 ms

gplus-16.png

gplus-16.png

94 ms

250x109xhortnet-logo-C.jpg.pagespeed.ic.N3p5m5ctRx.jpg

250x109xhortnet-logo-C.jpg.pagespeed.ic.N3p5m5ctRx.jpg

91 ms

500x109xseasonal.jpg.pagespeed.ic.Yzv66fPO7Q.jpg

500x109xseasonal.jpg.pagespeed.ic.Yzv66fPO7Q.jpg

111 ms

cookiecheck.pl

cookiecheck.pl

133 ms

xtwitter-bird-16x16.png.pagespeed.ic.HQeW9YkNi-.png

xtwitter-bird-16x16.png.pagespeed.ic.HQeW9YkNi-.png

128 ms

xfacebook-16x16.png.pagespeed.ic.jVUN2TlGYb.png

xfacebook-16x16.png.pagespeed.ic.jVUN2TlGYb.png

130 ms

cd.gif.pagespeed.ce.2JdGiI2i2V.gif

cd.gif.pagespeed.ce.2JdGiI2i2V.gif

127 ms

22x22xmallorn-sprout-22x22-green.gif.pagespeed.ic.0yNNHAJ6LW.png

22x22xmallorn-sprout-22x22-green.gif.pagespeed.ic.0yNNHAJ6LW.png

125 ms

plusone.js

plusone.js

130 ms

widgets.js

widgets.js

186 ms

ga.js

ga.js

83 ms

22x22xmallorn-sprout-22x22-red.gif.pagespeed.ic.o_MWGEgA_7.png

22x22xmallorn-sprout-22x22-red.gif.pagespeed.ic.o_MWGEgA_7.png

121 ms

rssfeed.png.pagespeed.ce.6NlFQ1ylwT.png

rssfeed.png.pagespeed.ce.6NlFQ1ylwT.png

134 ms

garauva11.jpg

garauva11.jpg

134 ms

dahlh40.jpg

dahlh40.jpg

134 ms

pussc00.jpg

pussc00.jpg

134 ms

impplpg40.jpg

impplpg40.jpg

133 ms

aritr00.jpg

aritr00.jpg

133 ms

irifc00.jpg

irifc00.jpg

177 ms

hemst41.jpg

hemst41.jpg

176 ms

lobhslp40.jpg

lobhslp40.jpg

174 ms

lobhslp00.jpg

lobhslp00.jpg

175 ms

hemcr40.jpg

hemcr40.jpg

174 ms

solsctrru10.jpg

solsctrru10.jpg

175 ms

hypanap41.jpg

hypanap41.jpg

220 ms

__utm.gif

__utm.gif

18 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

19 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

50 ms

fastbutton

fastbutton

152 ms

collect

collect

97 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

45 ms

postmessageRelay

postmessageRelay

52 ms

api.js

api.js

28 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

66 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

23 ms

follow_button.6a78875565a912489e9aef879c881358.en.html

follow_button.6a78875565a912489e9aef879c881358.en.html

41 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

37 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

31 ms

Accessibility Review

hort.net accessibility score

86

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

hort.net SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hort.net 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 Hort.net main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

hort.net

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