Report Summary

  • 84

    Performance

    Renders faster than
    88% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

reesfruitfarm.com

Welcome to Rees Fruit Farm

Page Load Speed

783 ms in total

First Response

88 ms

Resources Loaded

515 ms

Page Rendered

180 ms

reesfruitfarm.com screenshot

About Website

Welcome to reesfruitfarm.com homepage info - get ready to check Rees Fruit Farm best content right away, or after learning these important things about reesfruitfarm.com

apples, orchards, fruit, Rees, Fruit, Farm, Rees Fruit Farm, cider, Topeka

Visit reesfruitfarm.com

Key Findings

We analyzed Reesfruitfarm.com page load time and found that the first response time was 88 ms and then it took 695 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

reesfruitfarm.com performance score

84

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

37/100

25%

SI (Speed Index)

Value1.0 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.0 s

100/100

10%

Network Requests Diagram

reesfruitfarm.com

88 ms

email1_trans.gif

34 ms

Topeka.gif

165 ms

header_01.jpg

39 ms

header_09.jpg

95 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 77% of them (10 requests) were addressed to the original Reesfruitfarm.com, 15% (2 requests) were made to Banners.wunderground.com and 8% (1 request) were made to Img.constantcontact.com. The less responsive or slowest element that took the longest time to load (263 ms) relates to the external source Banners.wunderground.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 29.0 kB (5%)

Content Size

598.1 kB

After Optimization

569.1 kB

In fact, the total size of Reesfruitfarm.com main page is 598.1 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. Images take 569.2 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 25.2 kB

  • Original 28.9 kB
  • After minification 10.7 kB
  • After compression 3.7 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. This page needs HTML code to be minified as it can gain 18.2 kB, which is 63% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 25.2 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 3.8 kB

  • Original 569.2 kB
  • After minification 565.3 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. Rees Fruit Farm images are well optimized though.

Requests Breakdown

We found no issues to fix!

Requests Now

8

After Optimization

8

The browser has sent 8 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rees Fruit Farm. According to our analytics all requests are already optimized.

Accessibility Review

reesfruitfarm.com accessibility score

55

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

Best Practices

reesfruitfarm.com best practices score

50

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

reesfruitfarm.com 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

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Reesfruitfarm.com 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 Reesfruitfarm.com main page’s claimed encoding is . 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

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