Website review, no card needed

ribsandburgers.com logo

ribsandburgers.com website review

Visit site (opens in a new tab)Reviewed 24 October 202633 issues · 83 checks

This review found 33 issues worth fixing on ribsandburgers.com, 11 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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
4.9 s2.3 sMay 2Oct 174.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.8 s
May 9, 20262.7 s
May 16, 20262.6 s
May 23, 20262.6 s
May 30, 20262.9 s
Jun 6, 20263.2 s
Jun 13, 20263.5 s
Jun 20, 20263.7 s
Jun 27, 20263.7 s
Jul 4, 20263.7 s
Jul 11, 20263.7 s
Jul 18, 20263.8 s
Jul 25, 20264.0 s
Aug 1, 20264.1 s
Aug 8, 20264.2 s
Aug 15, 20264.3 s
Aug 22, 20264.5 s
Aug 29, 20264.5 s
Sep 5, 20264.6 s
Sep 12, 20264.5 s
Sep 19, 20264.4 s
Sep 26, 20264.4 s
Oct 3, 20264.4 s
Oct 10, 20264.5 s
Oct 17, 20264.6 s
Real-visitor tap response (INP)75th percentile, phones
160 ms109 msMay 2Oct 17154 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026120 ms
May 9, 2026121 ms
May 16, 2026117 ms
May 23, 2026115 ms
May 30, 2026121 ms
Jun 6, 2026123 ms
Jun 13, 2026130 ms
Jun 20, 2026137 ms
Jun 27, 2026130 ms
Jul 4, 2026128 ms
Jul 11, 2026126 ms
Jul 18, 2026125 ms
Jul 25, 2026130 ms
Aug 1, 2026138 ms
Aug 8, 2026140 ms
Aug 15, 2026140 ms
Aug 22, 2026140 ms
Aug 29, 2026137 ms
Sep 5, 2026141 ms
Sep 12, 2026137 ms
Sep 19, 2026131 ms
Sep 26, 2026137 ms
Oct 3, 2026139 ms
Oct 10, 2026146 ms
Oct 17, 2026154 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 ribsandburgers.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ribsandburgers.com at 0.6 s0.6 s
  2. ribsandburgers.com at 1.1 s1.1 s
  3. ribsandburgers.com at 1.7 s1.7 s
  4. ribsandburgers.com at 2.2 s2.2 s
  5. ribsandburgers.com at 2.8 s2.8 s
  6. ribsandburgers.com at 3.3 s3.3 s
  7. ribsandburgers.com at 3.9 s3.9 s
  8. ribsandburgers.com at 4.4 s4.4 s

Speed

10 to fix48
  • Reduce unused JavaScript

    2.4 s · 722 KiB

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

  • Use efficient cache lifetimes

    1.5 s · 342 KiB

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

  • Mobile performance score: 48

    48/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, TikTok and Facebook and others), adding 1.2 MB and 1.8 s of main-thread time.

  • Google Tag Manager adds 756 ms

    756 ms

    Google Tag Manager costs a phone 756 ms of main-thread work and 527 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.

  • TikTok adds 467 ms

    467 ms

    TikTok costs a phone 467 ms of main-thread work and 286 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.

  • Facebook adds 362 ms

    362 ms

    Facebook costs a phone 362 ms of main-thread work and 280 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.

  • Main-thread work: 3.9 s

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

  • 14 long tasks on the main thread

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

  • Legacy JavaScript

    300 ms · 42 KiB

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

  • Render-blocking requests

    150 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

  • Improve image delivery

    33 KiB

    1 image could be 33 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    14 KiB

    About 14 KiB of CSS is downloaded but never applied on this page.

  • Phones get a much slower page than desktops

    Desktop scores 83 but mobile only 48. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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.

1 checks passed
  • Server response: 203 ms

    203 ms

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

Core Web Vitals

9 to fix100
  • 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.

  • Largest Contentful Paint: 13.2 s

    13.2 s

    Your largest element takes 13.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “THE BEST BURGERS IN AUSTRALIA.”.

  • Time to Interactive: 14.2 s

    14.2 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Tap response (INP) got 24% slower for real visitors

    +24%

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

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

    +65%

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Speed Index: 4.9 s

    4.9 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

5 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 149 ms

    149 ms

    Real visitors wait 149 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.

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 7.0 MB in 93 requests

    7.0 MB

    Your homepage downloads 7.0 MB in 93 requests on a phone: media 4.1 MB (2), scripts 1.4 MB (40) and images 1.3 MB (23). Under 2 MB keeps phones on slow connections fast.

  • About 2.0 g of CO₂ per visit

    1.98 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.98 g of CO₂e: 238.0 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

6 to fixGoogle 9093
  • 9 tap targets too small

    9 tap targets are too small or too close together to hit reliably with a finger.

  • 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.

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

    All page content should be contained by landmarks: 18 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.

  • 6 links without text

    6 visible links have no text or label, so screen readers cannot say where they go.

  • ARIA role should be appropriate for the element (3 elements)

    ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 8 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • Structured data has 1 problem

    Structured data found (Article, FastFoodRestaurant, ImageObject and Organization) but with 1 problem, for example “Organization: url points at a different host (https://ribsaus.p11.sol1.net)”.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 61 internal links, 27 external

    The homepage links to 61 pages on ribsandburgers.com and 27 external pages.

7 checks passed
  • Meta description: 123 characters

    Your meta description is 123 characters: “Craving Ribs & Burgers? Stop in for the best burgers and mouth-watering ribs for dine-in, pick-up, or delivery in Austr…”.

  • One H1 headline

    Your main headline reads: “The Best Burgers In Australia.”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “The best burgers and ribs in Australia | Ribs & Burgers”.

  • Canonical URL set

    The canonical URL is https://ribsandburgers.com/au/.

  • 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 https://ribsandburgers.com/au/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (602 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without a meta description

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

  • 1 page slow to respond

    https://ribsandburgers.com/au/locations took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

6 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 an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 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”.

2 checks passed
  • Tap targets are thumb-sized

    12 of 13 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 446 words of copy

    The homepage carries about 446 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “ORDER”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Order Pickup”, “Order Delivery” and “Contact”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, TikTok Pixel and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok Pixel (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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies, 1 of them by other companies (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.

  • 18 other companies contacted

    Loading the homepage contacts 18 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 ribsandburgers.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 Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on ribsandburgers.com, including 19 speed issues, 2 SEO issues and 2 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