Website review, no card needed

articodental.com logo

articodental.com website review

Visit site (opens in a new tab)Reviewed 13 November 202623 issues · 74 checks

This review found 23 issues worth fixing on articodental.com, 10 of them high impact, across 74 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
3.7 s2.8 sMay 23Oct 103.5 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20263.0 s
May 30, 20262.9 s
Jun 6, 20263.0 s
Jul 4, 20263.3 s
Jul 25, 20263.2 s
Aug 1, 20263.2 s
Aug 8, 20263.3 s
Sep 19, 20263.6 s
Oct 10, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
110 ms78 msMay 23Oct 1092 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202686 ms
May 30, 202687 ms
Jun 6, 202687 ms
Jun 20, 202695 ms
Jul 4, 2026106 ms
Jul 18, 202693 ms
Jul 25, 202696 ms
Aug 1, 2026100 ms
Aug 8, 2026100 ms
Sep 19, 202682 ms
Oct 10, 202692 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 articodental.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix76
  • Render-blocking requests

    1.4 s

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

  • 3,075 HTML elements

    The page has 3,075 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Mobile performance score: 76

    76/100

    Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    710 KiB

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

  • Reduce unused CSS

    450 ms · 108 KiB

    About 108 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.

  • 2 third-party services on the page

    2 third-party services load with your homepage (adit.com and Google Fonts), adding 51 KiB and 23 ms of main-thread time.

  • Use efficient cache lifetimes

    14 KiB

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

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

2 checks passed
  • Main-thread work: 0.4 s

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

  • Server response: 50 ms

    50 ms

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

Core Web Vitals

5 to fix76
  • Largest Contentful Paint: 4.9 s

    4.9 s

    Your largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Welcome To Artico Dental Request Appointment”.

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

    +21%

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Speed Index: 4.5 s

    4.5 s

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

  • Time to Interactive: 4.9 s

    4.9 s

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • 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
  • Cumulative Layout Shift: 0

    0

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

  • 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

3 to fix65
  • 1 image over 500 KB

    Artico-Dental.jpg weighs 759 KiB. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (759 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.

  • 2 images far larger than shown

    216 KiB

    2 images are downloaded at several times the size a phone draws them, for example Artico-Dental.jpg at 1,366 px wide, shown at 390 px. Resized copies would save about 216 KiB.

  • About 0.5 g of CO₂ per visit

    0.46 g

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

2 checks passed
  • Page weight: 1.6 MB in 21 requests

    1.6 MB

    Your homepage downloads 1.6 MB in 21 requests on a phone: images 1.1 MB (5), fonts 275 KiB (4) and stylesheets 124 KiB (2). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

5 to fixGoogle 8391
  • 16 text elements with low contrast

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

  • Elements must only use permitted ARIA attributes (7 elements)

    Elements must only use permitted ARIA attributes: 7 elements on the page fail this check, rated serious by axe-core.

  • Frames without titles

    3 frames have no title, so screen-reader users cannot tell what they contain.

  • Links look like plain text

    2 links inside paragraphs rely on colour alone to stand out.

  • 2 tap targets too small

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 79 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 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 9290
  • Title is long (76 characters)

    Your title is 76 characters, so Google will cut it off around 60: “Dentist near me in Mesquite, Dallas & Duncanville, TX | Artico Dental + Kids”.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 358 internal links, 23 external

    The homepage links to 358 pages on articodental.com and 23 external pages.

7 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Are you Looking for a dentist near me in Mesquite, Dallas, or Duncanville, TX? Visit our Artico Dental + Kids dental of…”.

  • One H1 headline

    Your main headline reads: “Family Dentistry In Mesquite, Dallas & Duncanville”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://articodental.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://articodental.com/llms.txt (63 KiB, 250 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10084
  • 1 broken image

    1 image failed to load on a phone, for example https://articodental.com/.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    22 of 27 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
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No form on the homepage

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

  • 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 1,640 words of copy

    The homepage carries about 1,640 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 Appointment” and “Call Now”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Request Appointment”, “Contact Us” and “Learn More”.

  • Social proof on the page

    Social proof on the homepage: 41 testimonial or review blocks and 19 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 17 phone links and 0 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.

Privacy and tracking

  • 2 cookies set on arrival

    2

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

  • 3 other companies contacted

    Loading the homepage contacts 3 hosts 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 articodental.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2024.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Akamai Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on articodental.com, including 10 speed issues, 2 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