Website review, no card needed

teasdalelatinfoods.com logo

teasdalelatinfoods.com website review

Visit site (opens in a new tab)Reviewed 20 November 202639 issues · 68 checks

This review found 39 issues worth fixing on teasdalelatinfoods.com, 15 of them high impact, across 68 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.1 s1.4 sMay 30Nov 142.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.9 s
Jun 20, 20261.8 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.8 s
Jul 25, 20261.7 s
Aug 1, 20261.9 s
Aug 8, 20262.0 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.0 s
Sep 12, 20261.9 s
Sep 19, 20261.8 s
Sep 26, 20261.9 s
Oct 3, 20262.1 s
Oct 10, 20262.2 s
Oct 17, 20262.5 s
Oct 24, 20262.6 s
Oct 31, 20262.6 s
Nov 7, 20262.8 s
Nov 14, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
72 ms56 msMay 30Nov 1462 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202662 ms
Jun 6, 202658 ms
Jun 13, 202662 ms
Jun 20, 202664 ms
Jun 27, 202663 ms
Jul 4, 202670 ms
Jul 11, 202669 ms
Jul 18, 202663 ms
Jul 25, 202670 ms
Aug 1, 202663 ms
Aug 8, 202663 ms
Aug 15, 202669 ms
Aug 22, 202666 ms
Aug 29, 202669 ms
Sep 5, 202670 ms
Sep 12, 202665 ms
Sep 19, 202666 ms
Sep 26, 202668 ms
Oct 3, 202668 ms
Oct 10, 202661 ms
Oct 17, 202662 ms
Oct 24, 202663 ms
Oct 31, 202661 ms
Nov 7, 202662 ms
Nov 14, 202662 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of teasdalelatinfoods.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. teasdalelatinfoods.com at 0.8 s0.8 s
  2. teasdalelatinfoods.com at 1.6 s1.6 s
  3. teasdalelatinfoods.com at 2.4 s2.4 s
  4. teasdalelatinfoods.com at 3.1 s3.1 s
  5. teasdalelatinfoods.com at 3.9 s3.9 s
  6. teasdalelatinfoods.com at 4.7 s4.7 s
  7. teasdalelatinfoods.com at 5.5 s5.5 s
  8. teasdalelatinfoods.com at 6.3 s6.3 s

Speed

6 to fix67
  • Use efficient cache lifetimes

    4.0 s · 6.0 MB

    32 files are served with short cache lifetimes, so returning visitors download them again (6.0 MB).

  • Improve image delivery

    2.8 s · 1.6 MB

    3 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.8 s faster on a phone.

  • Render-blocking requests

    1.3 s

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

  • Mobile performance score: 67

    67/100

    Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    300 ms · 54 KiB

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

  • Font display

    300 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).

  • Chained critical requests

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 1 KiB and 0 ms of main-thread time.

2 checks passed
  • Main-thread work: 0.3 s

    A phone's processor spends 0.3 s on main-thread work while loading, 57 ms of it running JavaScript. That is comfortably low.

  • Server response: 32 ms

    32 ms

    Your server sent the HTML in 32 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user TTFB: 2.3 s

    2.3 s

    Real visitors wait 2.3 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest Contentful Paint: 5.3 s

    5.3 s

    Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (4.0 s).

  • Speed Index: 7.5 s

    7.5 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Largest content (LCP) got 60% slower for real visitors

    +60%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 2.7 s

    2.7 s

    Real visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.

  • Time to Interactive: 5.3 s

    5.3 s

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

  • Cumulative Layout Shift: 0.13

    0.13

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

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

3 checks passed
  • Real-user INP: 63 ms

    63 ms

    Real visitors wait 63 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix33
  • Page weight: 6.1 MB in 34 requests

    6.1 MB

    Your homepage downloads 6.1 MB in 34 requests on a phone: images 5.9 MB (18), scripts 88 KiB (7) and stylesheets 74 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • About 1.7 g of CO₂ per visit

    1.72 g

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

Accessibility

5 to fixGoogle 9068
  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 23 images without alt text

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

  • All page content should be contained by landmarks (2 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 checks passed
  • 6 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 9 WCAG 2.2 A/AA and best-practice rules on the phone render: 6 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9266
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is short (8 characters)

    Your title is only 8 characters: “Teasdale”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 42 internal links, 1 external

    The homepage links to 42 pages on teasdalelatinfoods.com and 1 external page.

3 checks passed
  • Canonical URL set

    The canonical URL is https://teasdalelatinfoods.com/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://teasdalelatinfoods.com/wp-sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    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.

  • No llms.txt

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

1 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Other pages

3 to fix65
  • 2 linked pages are broken

    Your homepage links to https://teasdalelatinfoods.com/facilities and https://teasdalelatinfoods.com/sustainability, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 page without a meta description

    https://teasdalelatinfoods.com/terms has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://teasdalelatinfoods.com/terms has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://teasdalelatinfoods.com/terms took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 1 page that loaded have a <title>.

Best practices

2 to fixGoogle 9689
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 503 ()”.

  • 5 distorted images

    5 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • No call to action on the first screen

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

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 22 words

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

  • No risk reducer

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

2 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “CONTACT US”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

Privacy and tracking

  • No consent tool detected

    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.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at teasdalelatinfoods.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Hosting
Crowncloud Gwy It Pty Ltd

Company

Employees
1,015
Headquarters
Carrollton

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on teasdalelatinfoods.com, including 17 speed issues, 5 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25