Report Summary

  • 92

    Performance

    Renders faster than
    92% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

clyderobin.com

Wildflower Seeds, Wildflower Mixes, Annual Wildflower Seed or Perennial Wildflower Seed

Page Load Speed

1.4 sec in total

First Response

277 ms

Resources Loaded

1.1 sec

Page Rendered

79 ms

clyderobin.com screenshot

About Website

Visit clyderobin.com now to see the best up-to-date Clyderobin content and also check out these interesting facts you probably never knew about clyderobin.com

Wildflower seed, wildflower seed mixes, and wildflowers seed blends for your garden. Find annual wildflowers and perennial wildflower mixes.

Visit clyderobin.com

Key Findings

We analyzed Clyderobin.com page load time and found that the first response time was 277 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 20% of websites can load faster.

Performance Metrics

clyderobin.com performance score

92

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

62/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

86/100

25%

SI (Speed Index)

Value2.8 s

95/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value2.7 s

97/100

10%

Network Requests Diagram

clyderobin.com

277 ms

siteground-optimizer-combined-css-f1e5f5e7878c4de32974ec063fb96f79.css

136 ms

css

28 ms

lazysizes.min.js

198 ms

neve-script.min.js

197 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 92% of them (12 requests) were addressed to the original Clyderobin.com, 8% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (291 ms) belongs to the original domain Clyderobin.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 50.9 kB (32%)

Content Size

158.3 kB

After Optimization

107.4 kB

In fact, the total size of Clyderobin.com main page is 158.3 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. 15% of websites need less resources to load. Javascripts take 75.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 31.3 kB

  • Original 39.9 kB
  • After minification 39.8 kB
  • After compression 8.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 31.3 kB or 79% of the original size.

JavaScript Optimization

-12%

Potential reduce by 9.3 kB

  • Original 75.2 kB
  • After minification 75.2 kB
  • After compression 65.9 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 9.3 kB or 12% of the original size.

CSS Optimization

-24%

Potential reduce by 10.2 kB

  • Original 43.2 kB
  • After minification 43.2 kB
  • After compression 33.0 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. Clyderobin.com needs all CSS files to be minified and compressed as it can save up to 10.2 kB or 24% of the original size.

Requests Breakdown

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

Requests Now

12

After Optimization

3

The browser has sent 12 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Clyderobin. 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.

Accessibility Review

clyderobin.com accessibility score

100

Accessibility Issues

Best Practices

clyderobin.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

clyderobin.com SEO score

92

Search Engine Optimization Advices

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Clyderobin.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 Clyderobin.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

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