Website review, no card needed
ritefoodsltd.com website review
Visit site (opens in a new tab)Reviewed 27 October 202638 issues · 80 checks
This review found 38 issues worth fixing on ritefoodsltd.com, 16 of them high impact, across 80 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
72CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 5.3 s |
| May 16, 2026 | 5.2 s |
| May 23, 2026 | 5.2 s |
| May 30, 2026 | 5.2 s |
| Jun 6, 2026 | 5.4 s |
| Jun 13, 2026 | 6.5 s |
| Jun 20, 2026 | 6.5 s |
| Jun 27, 2026 | 6.6 s |
| Jul 4, 2026 | 6.5 s |
| Jul 11, 2026 | 5.8 s |
| Jul 18, 2026 | 5.5 s |
| Jul 25, 2026 | 5.2 s |
| Aug 1, 2026 | 5.2 s |
| Aug 8, 2026 | 5.5 s |
| Aug 15, 2026 | 6.5 s |
| Aug 22, 2026 | 6.5 s |
| Aug 29, 2026 | 6.4 s |
| Sep 5, 2026 | 6.3 s |
| Sep 12, 2026 | 5.1 s |
| Sep 19, 2026 | 5.1 s |
| Sep 26, 2026 | 5.1 s |
| Oct 3, 2026 | 5.1 s |
| Oct 10, 2026 | 5.0 s |
| Oct 17, 2026 | 4.9 s |
| Oct 24, 2026 | 4.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 239 ms |
| May 16, 2026 | 203 ms |
| May 23, 2026 | 194 ms |
| May 30, 2026 | 202 ms |
| Jun 6, 2026 | 219 ms |
| Jun 13, 2026 | 363 ms |
| Jun 20, 2026 | 407 ms |
| Jun 27, 2026 | 457 ms |
| Jul 4, 2026 | 463 ms |
| Jul 11, 2026 | 357 ms |
| Jul 18, 2026 | 292 ms |
| Jul 25, 2026 | 218 ms |
| Aug 1, 2026 | 205 ms |
| Aug 8, 2026 | 256 ms |
| Aug 15, 2026 | 416 ms |
| Aug 22, 2026 | 429 ms |
| Aug 29, 2026 | 419 ms |
| Sep 5, 2026 | 416 ms |
| Sep 12, 2026 | 209 ms |
| Sep 19, 2026 | 184 ms |
| Sep 26, 2026 | 177 ms |
| Oct 3, 2026 | 178 ms |
| Oct 10, 2026 | 177 ms |
| Oct 17, 2026 | 167 ms |
| Oct 24, 2026 | 161 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.5 s
1.0 s
1.5 s
2.0 s
2.5 s
3.0 s
3.5 s
4.0 s
Speed
Render-blocking requests
2.5 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Reduce unused JavaScript
1.0 s · 272 KiBAbout 272 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.
Use efficient cache lifetimes
50 ms · 3.6 MB12 files are served with short cache lifetimes, so returning visitors download them again (3.6 MB).
Improve image delivery
3.4 MB12 images could be 3.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 58
58/100Your mobile performance score is 58 (desktop: 95). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Unpkg and others), adding 663 KiB and 534 ms of main-thread time.
Google Tag Manager adds 345 ms
345 msGoogle Tag Manager costs a phone 345 ms of main-thread work and 392 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.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 162 ms. During a long task the page ignores taps.
Legacy JavaScript
50 ms · 10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
Minify JavaScript
59 KiB59 KiB could be saved by minifying JavaScript.
Reduce unused CSS
11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 95 but mobile only 58. A gap that wide usually means heavy scripts and images that hit phones hardest.
Minify CSS
8 KiB8 KiB could be saved by minifying CSS.
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.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 635 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 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 LCP: 5.4 s
5.4 sReal visitors wait 5.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.3 s
4.3 sReal visitors see the first content after 4.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.9 s
1.9 sReal visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 8.0 s
8.0 sYour largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 16.2 s
16.2 sThe page becomes fully interactive after 16.2 s. Good is under 3.8 s.
Speed Index: 7.7 s
7.7 sVisually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
32 images without width and height
32 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.3 s to 4.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 143 ms
143 msReal visitors wait 143 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 26% faster for real visitors
-26%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 239 ms to 161 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 178 ms
178 msScripts block the page for only 178 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: 4.7 MB in 74 requests
4.7 MBYour homepage downloads 4.7 MB in 74 requests on a phone: images 3.8 MB (31), scripts 697 KiB (17) and fonts 96 KiB (3). Under 2 MB keeps phones on slow connections fast.
About 1.3 g of CO₂ per visit
1.33 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.33 g of CO₂e: 159.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No XML sitemap
No XML sitemap at https://www.ritefoodsltd.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at ritefoodsltd.com/robots.txt, the first file search crawlers ask for.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
5 internal links, 0 external
The homepage links to 5 pages on ritefoodsltd.com and 0 external pages.
2 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “We are a leading consumer packaged goods company in the Nigerian food and beverage industry, guided by a fanatical comm…”.
Title: 54 characters
Your title is a healthy 54 characters: “Rite Foods | Quality, Excellence, & Sustainable Growth”.
AI search readiness
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.
Some text only appears after JavaScript runs
34%The HTML your server sends has 136 of the 395 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://www.ritefoodsltd.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.
Other pages
5 pages without an H1
https://www.ritefoodsltd.com/about-us.html, https://www.ritefoodsltd.com/our-stories.html, https://www.ritefoodsltd.com/our-businesses/co2-plant.html, https://www.ritefoodsltd.com/careers.html and https://www.ritefoodsltd.com/privacy-policy.html have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://www.ritefoodsltd.com/our-stories.html, https://www.ritefoodsltd.com/our-businesses/co2-plant.html and https://www.ritefoodsltd.com/privacy-policy.html have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
5 internal pages checked
We fetched 5 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 5 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 5 pages that loaded have a meta description.
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 5 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
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.
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.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
About 395 words of copy
The homepage carries about 395 words of visible text.
2 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Learn More”.
Analytics in place
Analytics detected: Google Analytics and Cloudflare Web Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
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.
11 other companies contacted
Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 ritefoodsltd.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Cloudflare
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 ritefoodsltd.com, including 16 speed issues, 6 SEO issues and 3 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.