Website review, no card needed
caciquefoods.com website review
Visit site (opens in a new tab)Reviewed 18 November 202638 issues · 84 checks
This review found 38 issues worth fixing on caciquefoods.com, 16 of them high impact, across 84 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.1 s |
| Nov 7, 2026 | 2.1 s |
| Nov 14, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 86 ms |
| Jun 6, 2026 | 87 ms |
| Jun 13, 2026 | 87 ms |
| Jun 20, 2026 | 87 ms |
| Jun 27, 2026 | 87 ms |
| Jul 4, 2026 | 87 ms |
| Jul 11, 2026 | 87 ms |
| Jul 18, 2026 | 87 ms |
| Jul 25, 2026 | 93 ms |
| Aug 1, 2026 | 95 ms |
| Aug 8, 2026 | 95 ms |
| Aug 15, 2026 | 93 ms |
| Aug 22, 2026 | 88 ms |
| Aug 29, 2026 | 87 ms |
| Sep 5, 2026 | 86 ms |
| Sep 12, 2026 | 87 ms |
| Sep 19, 2026 | 86 ms |
| Sep 26, 2026 | 87 ms |
| Oct 3, 2026 | 86 ms |
| Oct 10, 2026 | 86 ms |
| Oct 17, 2026 | 87 ms |
| Oct 24, 2026 | 87 ms |
| Oct 31, 2026 | 88 ms |
| Nov 7, 2026 | 88 ms |
| Nov 14, 2026 | 87 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.4 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Reduce unused JavaScript
1.0 s · 167 KiBAbout 167 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.0 s faster on a phone.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
450 ms · 479 KiB11 images could be 479 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused CSS
330 ms · 85 KiBAbout 85 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 330 ms faster on a phone.
1,542 HTML elements
The page has 1,542 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Cookiebot and Google CDN and others), adding 490 KiB and 426 ms of main-thread time.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 147 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Use efficient cache lifetimes
35 KiB2 files are served with short cache lifetimes, so returning visitors download them again (35 KiB).
Minify JavaScript
10 ms · 5 KiB5 KiB could be saved by minifying JavaScript.
Legacy JavaScript
14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 538 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 CLS: 0.33
0.33For real visitors the layout shifts by 0.33 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 9.9 s
9.9 sYour largest element takes 9.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Time to Interactive: 10.0 s
10.0 sThe page becomes fully interactive after 10.0 s. Good is under 3.8 s.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 86 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 109 ms
109 msReal visitors wait 109 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 712 ms
712 msReal visitors wait 712 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 115 ms
115 msScripts block the page for only 115 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.5 MB in 86 requests
2.5 MBYour homepage downloads 2.5 MB in 86 requests on a phone: images 1.7 MB (29), scripts 555 KiB (28) and stylesheets 170 KiB (12). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
22 KiB2 images are downloaded at several times the size a phone draws them, for example since-1973.png at 400 px wide, shown at 133 px. Resized copies would save about 22 KiB.
5 images in older formats
5 images (369 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.
1 image below the first screen load straight away
1 image further down the page (124 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.72 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.72 g of CO₂e: 86.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Positive tabindex
2 elements have a tabindex above 0, which scrambles the keyboard order.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
18 images without alt text
18 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
62 internal links, 25 external
The homepage links to 62 pages on caciquefoods.com and 25 external pages.
7 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “Cacique Foods offers Mexican cheese, crema, chorizo, and salsa for tacos, dips, and family meals, plus recipes, product…”.
Title: 51 characters
Your title is a healthy 51 characters: “Cacique Foods Mexican Cheese, Crema, Chorizo, Salsa”.
Canonical URL set
The canonical URL is https://www.caciquefoods.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at http://www.caciquefoods.com/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
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.
3 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.
Text is in the HTML
Your server sends the page's text in the HTML (550 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.caciquefoods.com/llms.txt (133 KiB, 1,077 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
2 linked pages hidden from search
https://www.caciquefoods.com/product-category/shredded and https://www.caciquefoods.com/product-category/frozen-entrees are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
6 pages without a meta description
https://www.caciquefoods.com/about-cacique, https://www.caciquefoods.com/regeneration, https://www.caciquefoods.com/careers, https://www.caciquefoods.com/faq, https://www.caciquefoods.com/contact-us and https://www.caciquefoods.com/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages without an H1
https://www.caciquefoods.com/product-category/shredded, https://www.caciquefoods.com/product-category/frozen-entrees, https://www.caciquefoods.com/recipes, https://www.caciquefoods.com/regeneration, https://www.caciquefoods.com/products and https://www.caciquefoods.com/blog and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 19 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
18 small tap targets
18 of 34 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
A 11-field form
Your longest form asks for 11 fields (0 required). Every extra field lowers completion.
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 188 words
The homepage has only about 188 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
9 calls to action
The homepage has 9 calls to action, for example “Where To Buy”, “Sign up” and “Contact Us”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
12 other companies contacted
Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 caciquefoods.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
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Google Cloud
Hiring
- Hiring
- 12 open roles
- Job board
- adp
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on caciquefoods.com, including 13 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.