Website review, no card needed

diaglobal.org logo

diaglobal.org website review

Visit site (opens in a new tab)Reviewed 4 November 202640 issues · 86 checks

This review found 40 issues worth fixing on diaglobal.org, 16 of them high impact, across 86 checks. The most urgent: improve image delivery. 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
5.2 s3.7 sMay 16Oct 313.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.5 s
May 23, 20264.5 s
May 30, 20264.6 s
Jun 6, 20264.5 s
Jun 13, 20264.4 s
Jun 20, 20264.5 s
Jun 27, 20264.6 s
Jul 4, 20264.5 s
Jul 11, 20264.6 s
Jul 18, 20264.5 s
Jul 25, 20264.4 s
Aug 1, 20264.6 s
Aug 8, 20264.8 s
Aug 15, 20265.0 s
Aug 22, 20265.0 s
Aug 29, 20264.8 s
Sep 5, 20264.4 s
Sep 12, 20264.2 s
Sep 19, 20264.0 s
Sep 26, 20264.0 s
Oct 3, 20264.1 s
Oct 10, 20264.2 s
Oct 17, 20264.1 s
Oct 24, 20264.1 s
Oct 31, 20263.9 s
Real-visitor tap response (INP)75th percentile, phones
346 ms200 msMay 16Oct 31238 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026329 ms
May 23, 2026308 ms
May 30, 2026287 ms
Jun 6, 2026274 ms
Jun 13, 2026252 ms
Jun 20, 2026246 ms
Jun 27, 2026247 ms
Jul 4, 2026232 ms
Jul 11, 2026217 ms
Jul 18, 2026221 ms
Jul 25, 2026218 ms
Aug 1, 2026231 ms
Aug 8, 2026260 ms
Aug 15, 2026281 ms
Aug 22, 2026285 ms
Aug 29, 2026277 ms
Sep 5, 2026275 ms
Sep 12, 2026258 ms
Sep 19, 2026249 ms
Sep 26, 2026241 ms
Oct 3, 2026237 ms
Oct 10, 2026245 ms
Oct 17, 2026249 ms
Oct 24, 2026256 ms
Oct 31, 2026238 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 diaglobal.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. diaglobal.org at 4.2 s4.2 s
  2. diaglobal.org at 8.3 s8.3 s
  3. diaglobal.org at 12.5 s12.5 s
  4. diaglobal.org at 16.6 s16.6 s
  5. diaglobal.org at 20.8 s20.8 s
  6. diaglobal.org at 24.9 s24.9 s
  7. diaglobal.org at 29.1 s29.1 s
  8. diaglobal.org at 33.3 s33.3 s

Speed

10 to fix45
  • Improve image delivery

    33.7 s · 7.5 MB

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

  • Use efficient cache lifetimes

    3.8 s · 797 KiB

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

  • Render-blocking requests

    4.4 s

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

  • Reduce unused CSS

    2.4 s · 397 KiB

    About 397 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.4 s faster on a phone.

  • Reduce unused JavaScript

    1.8 s · 321 KiB

    About 321 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

  • Mobile performance score: 45

    45/100

    Your mobile performance score is 45. 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 (Google Tag Manager, Osano CMP and Hubspot and others), adding 1.0 MB and 1.1 s of main-thread time.

  • Google Tag Manager adds 698 ms

    698 ms

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

    350 ms · 25 KiB

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

  • Main-thread work: 2.4 s

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

  • Font display

    250 ms

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

  • 7 long tasks on the main thread

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

  • Minify CSS

    150 ms · 16 KiB

    16 KiB could be saved by minifying CSS.

  • Minify JavaScript

    150 ms · 13 KiB

    13 KiB could be saved by minifying JavaScript.

  • Document request latency

    106 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

1 checks passed
  • Server response: 246 ms

    246 ms

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

Core Web Vitals

11 to fix33
  • Fails Core Web Vitals for real visitors

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

  • Largest Contentful Paint: 57.6 s

    57.6 s

    Your largest element takes 57.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Industry Doesn't Wait. Neither Should You Early bird pr…”.

  • Time to Interactive: 58.0 s

    58.0 s

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

  • Speed Index: 14.8 s

    14.8 s

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

  • First Contentful Paint: 5.0 s

    5.0 s

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

  • Real-user LCP: 3.6 s

    3.6 s

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

  • Real-user CLS: 0.15

    0.15

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Total Blocking Time: 458 ms

    458 ms

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

  • 7 images without width and height

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

4 checks passed
  • Real-user INP: 177 ms

    177 ms

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

  • Tap response (INP) got 22% faster for real visitors

    -22%

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

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

    -12%

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

1 to fix70
  • Page weight: 11.9 MB in 101 requests

    11.9 MB

    Your homepage downloads 11.9 MB in 101 requests on a phone: images 9.9 MB (21), scripts 1.2 MB (41) and stylesheets 410 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (163 KiB) 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.

  • 2 images below the first screen load straight away

    2 images further down the page (158 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.4 g of CO₂ per visit

    3.36 g

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

1 checks passed
  • 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 8193
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 4 text elements with low contrast

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

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 6 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

5 to fixGoogle 8381
  • Title is long (94 characters)

    Your title is 94 characters, so Google will cut it off around 60: “Drug Information Association: The Global Network for Health Care Product Development Know…”.

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

  • 151 internal links, 15 external

    The homepage links to 151 pages on diaglobal.org and 15 external pages.

5 checks passed
  • Meta description: 94 characters

    Your meta description is 94 characters: “Drug Information Association: The Global Network for Health Care Product Development Knowledge”.

  • One H1 headline

    Your main headline reads: “The Industry Doesn't Wait. Neither Should You”.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.diaglobal.org/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.diaglobal.org/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 (550 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix75
  • 2 pages without a title

    https://www.diaglobal.org/api/sitecore/Language/LanguageRedirect and https://www.diaglobal.org/en/user/userid-help have no <title>, so Google invents the link text in results.

  • 2 pages without a meta description

    https://www.diaglobal.org/api/sitecore/Language/LanguageRedirect and https://www.diaglobal.org/en/user/userid-help have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.diaglobal.org/api/sitecore/Language/LanguageRedirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.diaglobal.org/en/general/global-events took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

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

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 9287
  • 6 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “__required is not defined”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 312 words of copy

    The homepage carries about 312 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Register for DIA 2027”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Create Account and Join”, “Download Catalog” and “Contact Us”.

  • 4 short forms

    4 short forms (3 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

  • 2 trackers load before any consent

    2

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

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies (measured from a US location before any click).

  • 5 other companies contacted

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

1 checks passed
  • Consent tool: Osano

    A consent management tool (Osano) 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 diaglobal.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Azure

Hiring

Hiring
4 open roles
Job board
careers page

Company

Employees
46

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on diaglobal.org, including 21 speed issues, 5 SEO issues 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