Website review, no card needed

datawords.com logo

datawords.com website review

Visit site (opens in a new tab)Reviewed 18 November 202631 issues · 80 checks

This review found 31 issues worth fixing on datawords.com, 12 of them high impact, across 80 checks. The most urgent: page weight: 57.3 MB in 136 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.5 s2.7 sMay 30Oct 243.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.3 s
Jun 6, 20263.3 s
Jun 13, 20263.2 s
Jun 20, 20263.2 s
Jun 27, 20263.4 s
Jul 4, 20263.2 s
Jul 11, 20263.1 s
Jul 18, 20263.0 s
Jul 25, 20262.8 s
Aug 1, 20262.8 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20263.0 s
Aug 29, 20263.0 s
Sep 19, 20263.2 s
Oct 3, 20262.9 s
Oct 10, 20262.8 s
Oct 17, 20263.1 s
Oct 24, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
221 ms126 msMay 30Oct 17154 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026205 ms
Jun 6, 2026210 ms
Jun 13, 2026180 ms
Jun 20, 2026153 ms
Jun 27, 2026143 ms
Jul 4, 2026138 ms
Jul 11, 2026139 ms
Jul 18, 2026137 ms
Jul 25, 2026138 ms
Aug 1, 2026139 ms
Aug 8, 2026147 ms
Aug 15, 2026171 ms
Aug 22, 2026150 ms
Aug 29, 2026163 ms
Oct 3, 2026170 ms
Oct 10, 2026178 ms
Oct 17, 2026154 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 datawords.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. datawords.com at 0.7 s0.7 s
  2. datawords.com at 1.4 s1.4 s
  3. datawords.com at 2.0 s2.0 s
  4. datawords.com at 2.7 s2.7 s
  5. datawords.com at 3.4 s3.4 s
  6. datawords.com at 4.1 s4.1 s
  7. datawords.com at 4.8 s4.8 s
  8. datawords.com at 5.4 s5.4 s

Speed

8 to fix59
  • Improve image delivery

    1.5 s · 2.9 MB

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

  • Render-blocking requests

    3.6 s

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

  • Mobile performance score: 59

    59/100

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

  • Reduce unused CSS

    750 ms · 182 KiB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Optanon and others), adding 1.1 MB and 435 ms of main-thread time.

  • Use efficient cache lifetimes

    350 ms · 130 KiB

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

  • Main-thread work: 3.6 s

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

  • kinsta.cloud adds 0 ms

    0 ms

    kinsta.cloud costs a phone 0 ms of main-thread work and 650 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.

  • Reduce unused JavaScript

    168 KiB

    About 168 KiB of JavaScript is downloaded but never used on this page.

  • Font display

    150 ms

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

  • 10 long tasks on the main thread

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

  • Minify CSS

    18 KiB

    18 KiB could be saved by minifying CSS.

  • Minify JavaScript

    13 KiB

    13 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

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

    108 ms

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

Core Web Vitals

5 to fix65
  • Largest Contentful Paint: 10.3 s

    10.3 s

    Your largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FLUENT IN EVERY MARKET”.

  • Time to Interactive: 25.6 s

    25.6 s

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

  • Speed Index: 9.4 s

    9.4 s

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

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • 28 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -6%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.1 s 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.

3 checks passed
  • Tap response (INP) got 20% faster for real visitors

    -20%

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

  • Total Blocking Time: 137 ms

    137 ms

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

  • Cumulative Layout Shift: 0.049

    0.049

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

Images and page weight

1 to fix70
  • Page weight: 57.3 MB in 136 requests

    57.3 MB

    Your homepage downloads 57.3 MB in 136 requests on a phone: media 51.0 MB (3), images 4.4 MB (30) and fonts 869 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (39 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 16.2 g of CO₂ per visit

    16.25 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 8391
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 2 tap targets too small

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

  • 4 images without alt text

    4 images have no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.

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

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

  • 3 links without text

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

  • Headings skip levels

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

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

4 to fixGoogle 7788
  • 6 H1 headlines

    There are 6 <h1> headlines (“connecting your brand”, “to the world” and “your Brand”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 18 links with vague text

    18 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 51 internal links, 8 external

    The homepage links to 51 pages on datawords.com and 8 external pages.

6 checks passed
  • Meta description: 133 characters

    Your meta description is 133 characters: “Datawords is a digital marketing agency that boosts the performance of international brands by making their content loc…”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “We connect brands to the world | Datawords”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and VideoObject.

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

AI search readiness

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

    Your Organization JSON-LD is missing 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.

  • No llms.txt

    There is no https://datawords.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.

2 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 (427 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix98
  • 4 pages share a meta description

    https://datawords.com/our-news and https://datawords.com/en/our-news use the same meta description. A description written for each page earns more clicks.

  • 3 pages slow to respond

    https://datawords.com/our-offices, https://datawords.com/en and https://datawords.com/en/our-news took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

2 to fixGoogle 9687
  • 6 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'offsetHeight')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

    The homepage carries about 257 words of visible text.

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “CONTACT US” and “Talk to an expert”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 58 cookies set on arrival

    58

    Opening the homepage sets 58 cookies, 5 of them by other companies (measured from a US location before any click).

  • 12 other companies contacted

    Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 datawords.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 Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on datawords.com, including 13 speed issues, 4 SEO issues and 3 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