Website review, no card needed

gdnonline.com logo

gdnonline.com website review

Visit site (opens in a new tab)Reviewed 18 November 202634 issues · 70 checks

This review found 34 issues worth fixing on gdnonline.com, 14 of them high impact, across 70 checks. The most urgent: page weight: 12.4 MB. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
10.1 s7.1 sMay 30Nov 147.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20268.4 s
Jun 6, 20268.5 s
Jun 13, 20268.4 s
Jun 20, 20268.3 s
Jun 27, 20268.5 s
Jul 4, 20269.3 s
Jul 11, 20269.6 s
Jul 18, 20269.5 s
Jul 25, 20269.7 s
Aug 1, 20269.4 s
Aug 8, 20269.3 s
Aug 15, 20269.2 s
Aug 22, 20268.3 s
Aug 29, 20267.8 s
Sep 5, 20267.6 s
Sep 12, 20268.0 s
Sep 19, 20268.0 s
Sep 26, 20268.0 s
Oct 3, 20268.0 s
Oct 10, 20268.1 s
Oct 17, 20268.1 s
Oct 24, 20267.9 s
Oct 31, 20267.7 s
Nov 7, 20267.5 s
Nov 14, 20267.4 s
Real-visitor tap response (INP)75th percentile, phones
150 ms127 msMay 30Nov 14138 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026130 ms
Jun 6, 2026130 ms
Jun 13, 2026130 ms
Jun 20, 2026131 ms
Jun 27, 2026132 ms
Jul 4, 2026136 ms
Jul 11, 2026139 ms
Jul 18, 2026141 ms
Jul 25, 2026143 ms
Aug 1, 2026145 ms
Aug 8, 2026147 ms
Aug 15, 2026146 ms
Aug 22, 2026145 ms
Aug 29, 2026143 ms
Sep 5, 2026143 ms
Sep 12, 2026143 ms
Sep 19, 2026144 ms
Sep 26, 2026143 ms
Oct 3, 2026141 ms
Oct 10, 2026141 ms
Oct 17, 2026142 ms
Oct 24, 2026143 ms
Oct 31, 2026142 ms
Nov 7, 2026143 ms
Nov 14, 2026138 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

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

5 to fix33
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user LCP: 7.3 s

    7.3 s

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

  • Real-user FCP: 6.4 s

    6.4 s

    Real visitors see the first content after 6.4 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.9 s

    1.9 s

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

  • Real-user CLS: 0.16

    0.16

    For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.

  • Tap response (INP) held steady for real visitors

    +8%

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

2 checks passed
  • Real-user INP: 136 ms

    136 ms

    Real visitors wait 136 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Largest content (LCP) got 12% faster for real visitors

    -12%

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

Images and page weight

5 to fix28
  • Page weight: 12.4 MB

    12.4 MB

    Your homepage downloads 12.4 MB on a phone, 9.6 MB of it images (77%). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    cover.jpg weighs 958 KiB. On a phone connection a single image that size takes seconds.

  • 17 images in older formats

    17 images (2.4 MB) are 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.

  • 11 images below the first screen load straight away

    11 images further down the page (1.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    433 KiB

    1 image is downloaded at several times the size a phone draws it, for example cover.jpg at 1,500 px wide, shown at 370 px. Resized copies would save about 433 KiB.

  • About 3.5 g of CO₂ per visit

    3.51 g

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

Accessibility

10 to fix86
  • 60 text elements with low contrast

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

  • 31 tap targets too small

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

  • 4 images without alt text

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

  • 103 links without text

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

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • No page language

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

  • Headings skip levels

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

1 checks passed
  • 43 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: 43 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fix72
  • Title is long (84 characters)

    Your title is 84 characters, so Google will cut it off around 60: “Gulf Digital News – Bahrain, Saudi Arabia, United Arab Emirates, Kuwait, Qatar, Oman”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 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 (513 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 447 internal links, 35 external

    The homepage links to 447 pages on gdnonline.com and 35 external pages.

2 checks passed
  • 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.gdnonline.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

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

Other pages

1 to fix93
  • 2 pages share a title

    https://www.gdnonline.com/index.html and https://www.gdnonline.com/Home all use the title “Gulf Digital News – Bahrain, Saudi Arabia, United Arab Emirates, Kuwa…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages slow to respond

    https://www.gdnonline.com/GroupSection/News, https://www.gdnonline.com/GroupSection/MiddleEastNews and https://www.gdnonline.com/Section/3/World-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 179 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    4 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • 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

2 to fix78
  • 3 broken images

    3 images failed to load on a phone, for example chrome-extension://invalid/.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    146 of 159 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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.

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

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

  • About 1,453 words of copy

    The homepage carries about 1,453 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “SUBSCRIBE |” and “CONTACT US”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

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.

  • 12 cookies set on arrival

    12

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

  • 26 other companies contacted

    Loading the homepage contacts 26 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 gdnonline.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
React
Analytics
Google Analytics

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 gdnonline.com, including 5 speed issues, 6 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