Website review, no card needed

rubys.com logo

rubys.com website review

Visit site (opens in a new tab)Reviewed 27 October 202619 issues · 76 checks

This review found 19 issues worth fixing on rubys.com, 5 of them high impact, across 76 checks. The most urgent: render-blocking requests. 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
2.3 s1.2 sMay 9Oct 241.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.1 s
May 16, 20262.2 s
May 23, 20262.0 s
May 30, 20261.7 s
Jun 6, 20261.5 s
Jun 13, 20261.4 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.5 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.7 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
89 ms80 msMay 9Oct 2487 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202681 ms
May 16, 202683 ms
May 23, 202684 ms
May 30, 202685 ms
Jun 6, 202686 ms
Jun 13, 202686 ms
Jun 20, 202685 ms
Jun 27, 202685 ms
Jul 4, 202683 ms
Jul 11, 202687 ms
Jul 18, 202687 ms
Jul 25, 202688 ms
Aug 1, 202687 ms
Aug 8, 202686 ms
Aug 15, 202685 ms
Aug 22, 202685 ms
Aug 29, 202687 ms
Sep 5, 202687 ms
Sep 12, 202687 ms
Sep 19, 202687 ms
Sep 26, 202687 ms
Oct 3, 202687 ms
Oct 10, 202687 ms
Oct 17, 202687 ms
Oct 24, 202687 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 rubys.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rubys.com at 0.5 s0.5 s
  2. rubys.com at 1.0 s1.0 s
  3. rubys.com at 1.5 s1.5 s
  4. rubys.com at 2.0 s2.0 s
  5. rubys.com at 2.5 s2.5 s
  6. rubys.com at 3.0 s3.0 s
  7. rubys.com at 3.5 s3.5 s
  8. rubys.com at 4.0 s4.0 s

Speed

3 to fix52
  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 52

    52/100

    Your mobile performance score is 52 (desktop: 86). Pages that score under 90 lose visitors before the first paint.

  • b-cdn.net adds 161 ms

    161 ms

    b-cdn.net costs a phone 161 ms of main-thread work and 892 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.

  • 1 third-party service on the page

    1 third-party service load with your homepage (b-cdn.net), adding 892 KiB and 161 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 60 KiB

    About 60 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    150 ms · 23 KiB

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

  • Improve image delivery

    51 KiB

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

  • Phones get a much slower page than desktops

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

  • Minify JavaScript

    10 KiB

    10 KiB could be saved by minifying JavaScript.

  • Minify CSS

    6 KiB

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

  • 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: 0.9 s

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

  • Server response: 56 ms

    56 ms

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

Core Web Vitals

6 to fix100
  • Cumulative Layout Shift: 0.981

    0.981

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

  • Largest Contentful Paint: 4.5 s

    4.5 s

    Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Fall into a pumpkin spice shake. ORDER NOW OPENS IN NEW WIN…”.

  • Speed Index: 5.2 s

    5.2 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Time to Interactive: 4.6 s

    4.6 s

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

  • 8 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +6%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user INP: 87 ms

    87 ms

    Real visitors wait 87 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.2 s

    1.2 s

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

  • Real-user TTFB: 707 ms

    707 ms

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

  • Largest content (LCP) got 24% faster for real visitors

    -24%

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

  • 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

100
  • About 0.3 g of CO₂ per visit

    0.26 g

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

4 checks passed
  • Page weight: 928 KiB in 54 requests

    928 KiB

    Your homepage downloads 928 KiB in 54 requests on a phone: images 712 KiB (27), scripts 143 KiB (5) and stylesheets 37 KiB (5). That is a lean page.

  • 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

Google 100100
2 checks passed
  • Every image has alt text

    All 29 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

3 to fixGoogle 10085
  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “Ruby's Diner - Classic Burgers, Handmade Shakes, Crispy Fries, and Fun”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Ruby's Diner” and “Want free burgers, shakes & more?”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 39 internal links, 26 external

    The homepage links to 39 pages on rubys.com and 26 external pages.

5 checks passed
  • Meta description: 98 characters

    Your meta description is 98 characters: “Serving Up Classic Burgers, Handmade Shakes, Crispy Fries, and Fun Since 1982. Now That's Classic!”.

  • Canonical URL set

    The canonical URL is https://www.rubys.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Restaurant, WebPage and WebSite.

  • 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://www.rubys.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.rubys.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 description; contact details would complete it.

  • Text is in the HTML

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

Other pages

3 to fix78
  • 1 page points its canonical at the homepage

    https://www.rubys.com/shake-shop declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.rubys.com/shake-shop all use the title “Ruby's Diner - Classic Burgers, Handmade Shakes, Crispy Fries, and Fun”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.rubys.com/rewards and https://www.rubys.com/opt-out-preferences have no meta description, so Google writes the search snippet from whatever text it finds.

  • 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
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 9697
  • 2 distorted images

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

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    37 of 39 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 501 words of copy

    The homepage carries about 501 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “ORDER” and “ORDER NOW OPENS IN NEW WINDOW”.

  • 18 calls to action

    The homepage has 18 calls to action, for example “Order”, “Order Now” and “Sign Up”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

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 other company contacted

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

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 rubys.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
Hosting
AWS

Company

Founded
1982
Headquarters
Irvine

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 19 issues on rubys.com, including 9 speed issues, 3 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

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