Website review, no card needed

royalcateringdfw.com logo

royalcateringdfw.com website review

Visit site (opens in a new tab)Reviewed 30 October 202627 issues · 77 checks

This review found 27 issues worth fixing on royalcateringdfw.com, 11 of them high impact, across 77 checks. The most urgent: improve image delivery. 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.6 s2.3 sJun 6Oct 103.2 s
Show as table
DateReal-visitor load time (LCP)
Jun 6, 20262.6 s
Jun 13, 20262.4 s
Jun 20, 20262.6 s
Jun 27, 20262.5 s
Sep 26, 20263.5 s
Oct 3, 20263.2 s
Oct 10, 20263.2 s

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 royalcateringdfw.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. royalcateringdfw.com at 0.4 s0.4 s
  2. royalcateringdfw.com at 0.8 s0.8 s
  3. royalcateringdfw.com at 1.1 s1.1 s
  4. royalcateringdfw.com at 1.5 s1.5 s
  5. royalcateringdfw.com at 1.9 s1.9 s
  6. royalcateringdfw.com at 2.3 s2.3 s
  7. royalcateringdfw.com at 2.6 s2.6 s
  8. royalcateringdfw.com at 3.0 s3.0 s

Speed

7 to fix43
  • Improve image delivery

    10.9 s · 2.8 MB

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

  • Use efficient cache lifetimes

    6.4 s · 1.6 MB

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

  • Render-blocking requests

    1.4 s

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

  • Reduce unused CSS

    1.1 s · 185 KiB

    About 185 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 43

    43/100

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

  • Reduce unused JavaScript

    600 ms · 159 KiB

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

  • Font display

    600 ms

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

  • Legacy JavaScript

    200 ms · 13 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Clarity and Google Fonts and others), adding 235 KiB and 186 ms of main-thread time.

  • 3 long tasks on the main thread

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

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

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

  • Server response: 86 ms

    86 ms

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

Core Web Vitals

6 to fix40
  • Largest Contentful Paint: 21.6 s

    21.6 s

    Your largest element takes 21.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “OUR JOB IS TO MAKE YOUR JOB EASIER Office Catering, Special…”.

  • Time to Interactive: 21.8 s

    21.8 s

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

  • Speed Index: 8.4 s

    8.4 s

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

  • Cumulative Layout Shift: 0.453

    0.453

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

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

    +28%

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

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Total Blocking Time: 45 ms

    45 ms

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

Images and page weight

1 to fix70
  • Page weight: 4.4 MB in 105 requests

    4.4 MB

    Your homepage downloads 4.4 MB in 105 requests on a phone: images 3.4 MB (14), scripts 561 KiB (79) and stylesheets 201 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (354 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.

  • 4 images below the first screen load straight away

    4 images further down the page (144 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.2 g of CO₂ per visit

    1.23 g

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

1 checks passed
  • 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 8992
  • 3 images without alt text

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

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

1 checks passed
  • 39 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: 39 passed and 7 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 8586
  • Title is short (25 characters)

    Your title is only 25 characters: “Home - Royal Catering DFW”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (236 characters)

    Your meta description is 236 characters; Google truncates after about 160, so the end of your pitch is cut.

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

  • 32 internal links, 5 external

    The homepage links to 32 pages on royalcateringdfw.com and 5 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “OUR JOB IS TO MAKE YOUR JOB EASIER”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, FoodEstablishment, ImageObject, Organization and Place.

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

AI search readiness

100
  • No llms.txt

    There is no https://royalcateringdfw.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 (591 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 page without a meta description

    https://royalcateringdfw.com/bar-service has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://royalcateringdfw.com/service-styles, https://royalcateringdfw.com/bar-service and https://royalcateringdfw.com/delivery-setup-pickup have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages with very little text

    https://royalcateringdfw.com/menus, https://royalcateringdfw.com/breakfast-brunch, https://royalcateringdfw.com/breaks, https://royalcateringdfw.com/individual-boxed-meals, https://royalcateringdfw.com/appetizers and https://royalcateringdfw.com/events 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.

  • 15 internal pages checked

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

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

  • 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

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    30 of 31 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • Thin social proof

    Social proof on the homepage: 81 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 641 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “REQUEST A QUOTE”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Join Our Team” and “Request a Quote”.

  • Analytics in place

    Analytics detected: Google Analytics and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 1 email link.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • 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

1 to fix
  • 3 trackers load before any consent

    3

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

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 8 other companies contacted

    Loading the homepage contacts 8 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 royalcateringdfw.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 | Microsoft Clarity
Hosting
Newfold Digital

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on royalcateringdfw.com, including 13 speed issues, 3 SEO issues and 1 conversion gap. 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