wishfarms.com website review

About 538 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.

15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

About 149 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

Your mobile performance score is 60 (desktop: 69). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Vimeo, jQuery CDN and cdn-cookieyes.com and others), adding 6.3 MB and 195 ms of main-thread time.

Vimeo costs a phone 78 ms of main-thread work and 5.9 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

A phone's processor spends 2.4 s on main-thread work while loading, 863 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 1,528 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Polyfills for old browsers add 29 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

7 KiB could be saved by minifying CSS.

4 images could be 121 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

4 long tasks block the main thread while loading, the longest for 68 ms. During a long task the page ignores taps.

6 files are served with short cache lifetimes, so returning visitors download them again (57 KiB).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Spooky recipes banner”.

The page becomes fully interactive after 14.2 s. Good is under 3.8 s.

The first text or image appears after 5.0 s on a phone. Good is under 1.8 s.

Visually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.

Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 99 ms to 256 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

16 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 7.5 MB in 116 requests on a phone: other files 5.4 MB (15), scripts 1.0 MB (36) and images 551 KiB (38). Under 2 MB keeps phones on slow connections fast.

Website-Homepage-banner-MOBILE-600-×-400-px-1.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

By the Sustainable Web Design model, a visit to your homepage emits about 2.14 g of CO₂e: 256.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

13 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 links have no real href, so search engines can't follow them.

The homepage links to 87 pages on wishfarms.com and 54 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://wishfarms.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://wishfarms.com/family-foundation and https://wishfarms.com/blog have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 51 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://wishfarms.com/.

8 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 161 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 8 cookies, 2 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.