Website review, no card needed

artofcatering.net logo

artofcatering.net website review

Visit site (opens in a new tab)Reviewed 23 October 202628 issues · 78 checks

This review found 28 issues worth fixing on artofcatering.net, 8 of them high impact, across 78 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

Full-page screenshot of artofcatering.net (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix61
  • Reduce unused JavaScript

    2.7 s · 503 KiB

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

  • Render-blocking requests

    2.6 s

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

  • Mobile performance score: 61

    61/100

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

  • Improve image delivery

    450 ms · 342 KiB

    4 images could be 342 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google CDN, website-files.com and cloudfront.net and others), adding 4.0 MB and 222 ms of main-thread time.

  • website-files.com adds 87 ms

    87 ms

    website-files.com costs a phone 87 ms of main-thread work and 3.6 MB 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.

  • Google CDN adds 106 ms

    106 ms

    Google CDN costs a phone 106 ms of main-thread work and 348 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 126 ms. During a long task the page ignores taps.

  • Font display

    50 ms

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

  • 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 93 but mobile only 61. 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.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.8 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

5 to fix66
  • Largest Contentful Paint: 22.7 s

    22.7 s

    Your largest element takes 22.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 22.7 s

    22.7 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Speed Index: 5.8 s

    5.8 s

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

  • 4 images without width and height

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

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

2 checks passed
  • Total Blocking Time: 101 ms

    101 ms

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

  • 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: 4.4 MB in 25 requests

    4.4 MB

    Your homepage downloads 4.4 MB in 25 requests on a phone: images 3.5 MB (7), scripts 884 KiB (10) and fonts 54 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (60 KiB) is 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 (60 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.3 g of CO₂ per visit

    1.26 g

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

5 to fixGoogle 8790
  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • 3 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

2 checks passed
  • Every image has alt text

    All 6 images in the HTML carry an alt attribute.

  • 24 automated accessibility rules passed

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

SEO

5 to fixGoogle 10075
  • Title is long (80 characters)

    Your title is 80 characters, so Google will cut it off around 60: “Art of Catering - Full Service Wedding and Corporate Catering in Portland Oregon”.

  • 4 H1 headlines

    There are 4 <h1> headlines (“Welcome”, “What's the occasion?” and “Have a seat”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (515 characters)

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

  • Structured data has 1 problem

    Structured data found (FoodEstablishment) but with 1 problem, for example “FoodEstablishment: url is not an absolute URL ("/")”.

  • 16 internal links, 2 external

    The homepage links to 16 pages on artofcatering.net and 2 external pages.

3 checks passed
  • 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://www.artofcatering.net/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.artofcatering.net/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, description and contact details; sameAs (social profiles) would complete it.

  • Text is in the HTML

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

Other pages

1 to fix98
  • 4 pages share a meta description

    https://www.artofcatering.net/services, https://www.artofcatering.net/food-drink, https://www.artofcatering.net/philosophy and https://www.artofcatering.net/contact use the same meta description. A description written for each page earns more clicks.

  • 1 page with very little text

    https://www.artofcatering.net/contact has 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.

  • 4 internal pages checked

    We fetched 4 pages linked from your homepage and read each the way a search engine does.

7 checks passed
  • Linked pages load

    All 4 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 4 pages that loaded have a meta description.

  • 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 4 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 small tap targets

    2 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Only about 203 words

    The homepage has only about 203 words of visible text; thin pages give Google and first-time buyers little to go on.

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Call Us” and “CONTACT”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “Call Us” and “Start Planning Your Event”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

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

    3

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

  • 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 artofcatering.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on artofcatering.net, including 12 speed issues, 5 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