Website review, no card needed

aria-atl.com logo

aria-atl.com website review

Visit site (opens in a new tab)Reviewed 28 October 202634 issues · 86 checks

This review found 34 issues worth fixing on aria-atl.com, 15 of them high impact, across 86 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
1.3 s1.0 sMay 9Oct 241.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.1 s
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.3 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
72 ms62 msMay 9Oct 2465 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202668 ms
May 16, 202668 ms
May 23, 202667 ms
May 30, 202668 ms
Jun 6, 202664 ms
Jun 13, 202670 ms
Jun 20, 202668 ms
Jun 27, 202668 ms
Jul 4, 202669 ms
Jul 11, 202664 ms
Jul 18, 202667 ms
Jul 25, 202668 ms
Aug 1, 202669 ms
Aug 8, 202671 ms
Aug 15, 202671 ms
Aug 22, 202670 ms
Aug 29, 202671 ms
Sep 5, 202667 ms
Sep 12, 202670 ms
Sep 19, 202671 ms
Sep 26, 202671 ms
Oct 3, 202668 ms
Oct 10, 202663 ms
Oct 17, 202668 ms
Oct 24, 202665 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 aria-atl.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

12 to fix38
  • Reduce unused JavaScript

    6.4 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.4 s faster on a phone.

  • Render-blocking requests

    2.9 s

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

  • Use efficient cache lifetimes

    1.1 s · 225 KiB

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

  • Mobile performance score: 38

    38/100

    Your mobile performance score is 38 (desktop: 42). 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 (Squarespace, Google CDN and Google Tag Manager and others), adding 2.7 MB and 1.6 s of main-thread time.

  • Squarespace adds 813 ms

    813 ms

    Squarespace costs a phone 813 ms of main-thread work and 1.3 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.

  • Reduce unused CSS

    450 ms · 216 KiB

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

  • Google CDN adds 460 ms

    460 ms

    Google CDN costs a phone 460 ms of main-thread work and 798 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.

  • Legacy JavaScript

    400 ms · 119 KiB

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

  • Main-thread work: 3.4 s

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

  • 13 long tasks on the main thread

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

  • Google Tag Manager adds 218 ms

    218 ms

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

  • Improve image delivery

    100 ms · 156 KiB

    2 images could be 156 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

  • Minify JavaScript

    130 ms · 16 KiB

    16 KiB could be saved by minifying JavaScript.

  • Font display

    100 ms

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

  • 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: 51 ms

    51 ms

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

Core Web Vitals

6 to fix100
  • First Contentful Paint: 7.8 s

    7.8 s

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

  • Largest Contentful Paint: 22.5 s

    22.5 s

    Your largest element takes 22.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Join us October 26-31 for a special four-course menu ($90 p…”.

  • Time to Interactive: 25.5 s

    25.5 s

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

  • Speed Index: 9.8 s

    9.8 s

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

  • Total Blocking Time: 749 ms

    749 ms

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

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

    1.3 s

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

  • Real-user INP: 62 ms

    62 ms

    Real visitors wait 62 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: 529 ms

    529 ms

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

  • Cumulative Layout Shift: 0.032

    0.032

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

Images and page weight

1 to fix70
  • Page weight: 4.2 MB in 129 requests

    4.2 MB

    Your homepage downloads 4.2 MB in 129 requests on a phone: scripts 2.8 MB (77), other files 542 KiB (12) and images 316 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • About 1.2 g of CO₂ per visit

    1.20 g

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

5 to fixGoogle 9392
  • 12 text elements with low contrast

    12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Links must have discernible text (9 elements)

    Links must have discernible text: 9 elements on the page fail this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • 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 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

1 to fixGoogle 10096
  • Structured data has 2 problems

    Structured data found (LocalBusiness, Organization, Restaurant and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/53d6cfc4e4b08c04192…”.

  • 60 internal links, 15 external

    The homepage links to 60 pages on aria-atl.com and 15 external pages.

7 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Discover modern American cuisine, exceptional wines, and thoughtful hospitality at one of Atlanta’s most celebrated din…”.

  • One H1 headline

    Your main headline reads: “Modern American Cuisine, Fine Dining in Buckhead, Atlanta - Aria Restaurant”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Fine Dining Restaurant in Buckhead, Atlanta | Aria”.

  • Canonical URL set

    The canonical URL is https://www.aria-atl.com/.

  • 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.aria-atl.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

Other pages

3 to fix86
  • 10 pages share 5 titles

    https://www.aria-atl.com/dinner-dessert and https://www.aria-atl.com/food-wine all use the title “Modern American Cuisine | Dinner & Dessert Menu | Aria Atlanta”, and 4 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 10 pages share a meta description

    https://www.aria-atl.com/dinner-dessert and https://www.aria-atl.com/food-wine use the same meta description. A description written for each page earns more clicks.

  • 5 links to non-canonical URLs

    Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.aria-atl.com/food-wine, whose canonical is https://www.aria-atl.com/dinner-dessert. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 16 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

3 to fixGoogle 7385
  • 6 third-party cookies

    6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix78
  • 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 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 623 words of copy

    The homepage carries about 623 words of visible text.

7 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Join Our Team” and “Sign Up”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

  • 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
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 5 cookies set on arrival

    5

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

  • 20 other companies contacted

    Loading the homepage contacts 20 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 aria-atl.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
Squarespace
Framework
jQuery
Analytics
Google Analytics
Hosting
Squarespace

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on aria-atl.com, including 18 speed issues, 1 SEO issue 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