SEO report

SEO report for www.dialpad.com

https://www.dialpad.com/ · checked Sun, 01 Nov 2026 16:04 GMT

✓ 36 Passed! 5 Warnings✗ 9 FailedAI readiness 94%

Fix these first

  1. Render-blocking resourceshigh

    1 blocking script(s) and 7 stylesheet(s) in <head>.

    Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.

    See the details

  2. LocalBusiness markuphigh

    No LocalBusiness structured data.

    Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.

    See the details

  3. HTML sizemedium

    435 kB of HTML – heavy for phones.

    Fix: Remove inline bloat, base64 images and unused markup.

    See the details

  4. Scripts & third partiesmedium

    151 script tag(s); files loaded from 3 other domain(s): images.ctfassets.net, fast.wistia.com, consent.app.relyance.ai.

    Fix: Remove unused tracking and widget scripts; every third party adds connection time.

    See the details

  5. Imagesmedium

    42 image(s).

    Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.

    See the details

  6. Form labelsmedium

    2 of 2 form field(s) have no label.

    Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).

    See the details

  7. Readabilitymedium

    Flesch reading ease 44 (fairly difficult), about 13 words per sentence.

    Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.

    See the details

  8. Heading structuremedium

    20 headings for 778 words – a lot for the amount of text.

    Fix: Use H2s for main sections and H3s inside them, without skipping levels.

    See the details

Check the whole website

This report covers one page. The full-site audit crawls up to 250 pages to find broken links, duplicate titles, orphan pages and more.

Run a full-site audit

Monitor this site weekly

We'll re-check it every week and track the score, with a history graph and a list of anything that breaks.

Compare with competitors

See how this page scores against up to two competitors, side by side, and where they beat you.

Compare sites

Real-world speed Google PageSpeed

Loading Core Web Vitals from Google… this can take up to 30 seconds.

Authority & backlinks

Looking up which websites link to dialpad.com…

Indexing & crawling 100%

Can search engines reach, read and index this page?

  • ✓

    Status codecritical

    The page returned HTTP 200.

  • ✓

    Indexablecritical

    No noindex instruction – the page can appear in search.

  • ✓

    robots.txthigh

    robots.txt found.

    Googlebot is allowed to crawl this page.

  • ✓

    XML sitemaphigh

    Sitemap index found at https://www.dialpad.com/sitemap.xml listing 27 sitemaps.

    Declared in robots.txt.

    Most recent lastmod: 2026-10-30T21:45:02.453Z.

  • ✓

    Canonical URLhigh

    Canonical: https://www.dialpad.com/

    Points to this page (self-referencing).

  • ✓

    Redirectshigh

    1 redirect before the page loaded.

    https://dialpad.com/ → https://www.dialpad.com/

    A single redirect to your preferred address is normal; just make sure your own links use the final address.

  • ✓

    www / non-wwwmedium

    dialpad.com redirects to www.dialpad.com.

  • ✓

    hreflangmedium

    6 hreflang link(s).

    All language codes are valid.

Search snippet & sharing 100%

How the page looks in Google results and when shared.

  • ✓

    Title tagcritical

    “AI Customer Experience Platform | Agentic CX | Dialpad”

    About 497px of Google's ~580px desktop width.

  • ✓

    Meta descriptionhigh

    159 characters, ~979px of ~990px.

    Good length.

    Google sometimes rewrites descriptions to match the search; a good one is still used most often.

  • ✓

    Open Graph & social cardsmedium

    Open Graph title and image set.

    Twitter/X card: summary.

  • ✓

    Faviconlow

    Favicon linked (Google shows it next to results).

  • ✓

    Languagelow

    lang="en-US"

Content quality 80%

Is there enough clear, useful text that matches what the page targets?

  • ✓

    Word countmedium

    778 words of main content (inside <main>).

    Google has no minimum word count – this is a rough guide to whether the page answers the question in full.

  • !

    Readabilitymedium

    Flesch reading ease 44 (fairly difficult), about 13 words per sentence.

    Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.

  • ✓

    Topic focushigh

    4 of 4 title keywords appear in the main content.

  • ✓

    H1 headingcritical

    “The AI platform for customer experience”

  • !

    Heading structuremedium

    20 headings for 778 words – a lot for the amount of text.

    Levels are in order.

    Fix: Use H2s for main sections and H3s inside them, without skipping levels.

  • ✗

    Text-to-code ratiolow

    2% of the HTML is visible text.

    Fix: Trim unused markup, inline scripts and builder bloat.

AI search readiness 94%

Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?

  • ✓

    AI crawler accesshigh

    Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.

  • ✓

    Snippet controlshigh

    No snippet restrictions – search and AI answers can quote this page.

  • ✓

    llms.txtlow

    /llms.txt found.

  • !

    Question-led contentmedium

    1 heading(s) phrased as questions, e.g. “Your customers are telling you what to do next. Can your business hear”.

    Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.

  • ✓

    Entity clarityhigh

    Identified as: Organization, Person.

    5 official profile link(s) (sameAs).

  • ✓

    Freshness signalsmedium

    The page shows when it was published or last updated.

  • ✓

    Trust pages (E-E-A-T)medium

    Links found to all three: about, contact and privacy.

Structured data 100%

Machine-readable facts for rich results and AI.

  • ✓

    JSON-LD present & validhigh

    1 JSON-LD block(s): Organization, PostalAddress, Person, Place, ImageObject, WebPage, BreadcrumbList, ListItem.

    All blocks parse correctly.

  • ✓

    Required propertiesmedium

    Key types include Google's required properties.

  • i

    Breadcrumbslow

    Home page – breadcrumbs not needed.

Performance 27%

Speed signals from the HTML and server. Real-user Core Web Vitals load below.

  • ✓

    Server response (TTFB)high

    105 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).

  • ✗

    HTML sizemedium

    435 kB of HTML – heavy for phones.

    Fix: Remove inline bloat, base64 images and unused markup.

  • i

    Compressionmedium

    Couldn't be measured from our server (our fetch decodes compressed pages before we see them). Check in your browser's developer tools that HTML is sent with br or gzip.

  • ✗

    Render-blocking resourceshigh

    1 blocking script(s) and 7 stylesheet(s) in <head>.

    Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.

  • ✗

    Scripts & third partiesmedium

    151 script tag(s); files loaded from 3 other domain(s): images.ctfassets.net, fast.wistia.com, consent.app.relyance.ai.

    Fix: Remove unused tracking and widget scripts; every third party adds connection time.

  • ✗

    Imagesmedium

    42 image(s).

    13 without width/height – can cause layout shift (CLS).

    5 image(s) after the first three aren't lazy-loaded.

    31 use WebP/AVIF or responsive srcset.

    Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.

  • !

    Cachinglow

    Cache-Control: public, max-age=0, must-revalidate

    Fix: Set Cache-Control so browsers and CDNs can reuse the page.

  • i

    HTTP/3low

    Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.

Security 92%

Visitor safety signals that browsers and Google check.

  • ✓

    HTTPScritical

    Secure HTTPS with no mixed content.

  • ✓

    HTTP → HTTPS redirecthigh

    http:// redirects to https://.

  • ✓

    HSTSmedium

    HSTS: max-age=63072000

  • ✓

    Security headerslow

    Present: CSP, nosniff, Referrer-Policy, clickjacking protection.

  • ✗

    Server fingerprintlow

    X-Powered-By reveals “Next.js”.

    Fix: Remove X-Powered-By so attackers can't see your software versions.

Mobile & accessibility 83%

Usable on phones and by everyone – Google indexes the mobile version.

  • ✓

    Mobile viewportcritical

    viewport: width=device-width, initial-scale=1

  • ✓

    Image alt textmedium

    All 42 images have alt text.

  • ✗

    Form labelsmedium

    2 of 2 form field(s) have no label.

    Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).

  • ✓

    Tap-to-contactmedium

    One-tap contact: phone.

Local SEO 33%

Signals that help you appear in Google Maps and 'near me' searches.

This report checks one page. Scores are a guide, not a guarantee of rankings. Check another page · Print or save as PDF

Want these fixed for you? XKey is made by IceWork, a Blackpool web studio. IceWork builds fast websites that pass every check here – a 3-page site with domain and a year's hosting is £350 all in.