redpotatomarket.com website review

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, cloudfront.net and Stripe and others), adding 5.6 MB and 1.1 s of main-thread time.

About 364 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 610 ms faster on a phone.

cloudfront.net costs a phone 228 ms of main-thread work and 3.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.

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

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

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

Stripe costs a phone 184 ms of main-thread work and 304 KiB 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.

marsello.app costs a phone 134 ms of main-thread work and 716 KiB 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.

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

Polyfills for old browsers add 21 KiB JavaScript that modern phones do not need.

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.

Your largest element takes 13.4 s to render on a phone. Google's threshold for “good” is 2.5 s.

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

The layout shifts by 0.255 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Scripts block taps and scrolling for 320 ms in total while the page loads. Good is under 200 ms.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 5.8 MB in 179 requests on a phone: images 2.6 MB (56), scripts 2.3 MB (63) and stylesheets 507 KiB (26). Under 2 MB keeps phones on slow connections fast.

17 images further down the page (1.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

14 images (733 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

2 images are downloaded at several times the size a phone draws them, for example JbfgoMe-1200x1200.webp at 2,000 px wide, shown at 390 px. Resized copies would save about 228 KiB.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (33 elements).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 100 characters, so Google will cut it off around 60: “Red Potato Market | Women’s Boutique Clothing, Gifts, Baby & Home Decor – Texas Boutique …”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is 308 characters; Google truncates after about 160, so the end of your pitch is cut.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 60 pages on redpotatomarket.com and 7 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.redpotatomarket.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.

Your homepage links to https://www.redpotatomarket.com/tiktok.com/@redpotatomarket, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.redpotatomarket.com/products/%F0%9D%90%82%F0%9D%90%87%F0%9D%90%91%F0%9D%90%88%F0%9D%90%92%F0%9D%90%93%F0%9D%90%8C%F0%9D%90%80%F0%9D%90%92%F0%9F%8E%84, https://www.redpotatomarket.com/products/%F0%9D%90%85%F0%9D%90%80%F0%9D%90%8B%F0%9D%90%8B%F0%9F%A6%83 and https://www.redpotatomarket.com/products/%F0%9D%90%85%F0%9D%90%88%F0%9D%90%8D%F0%9D%90%80%F0%9D%90%8B-%F0%9D%90%92%F0%9D%90%80%F0%9D%90%8B%F0%9D%90%84 have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.redpotatomarket.com/products/Store-&-Vendor-Events-c160298503, whose canonical is https://www.redpotatomarket.com/products/store--vendor-events. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 (Too Many Requests)”.

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.

There is no form on the homepage, so every lead has to click through to another page first.

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

The homepage carries about 580 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag and 1 more (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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