Website review, no card needed

globalinitiative.net logo

globalinitiative.net website review

Visit site (opens in a new tab)Reviewed 29 October 202647 issues · 91 checks

This review found 47 issues worth fixing on globalinitiative.net, 23 of them high impact, across 91 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
2.4 s2.1 sMay 9Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.1 s
May 16, 20262.1 s
May 23, 20262.2 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.1 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
122 ms89 msMay 9Oct 2495 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202693 ms
May 16, 202693 ms
May 23, 202693 ms
May 30, 2026104 ms
Jun 6, 2026105 ms
Jun 13, 2026106 ms
Jun 20, 2026102 ms
Jun 27, 2026104 ms
Jul 4, 2026113 ms
Jul 11, 2026113 ms
Jul 18, 2026114 ms
Jul 25, 2026118 ms
Aug 1, 202699 ms
Aug 8, 202697 ms
Aug 15, 202698 ms
Aug 22, 202696 ms
Aug 29, 202697 ms
Sep 5, 202698 ms
Sep 12, 202694 ms
Sep 19, 202694 ms
Sep 26, 202695 ms
Oct 3, 202695 ms
Oct 10, 202696 ms
Oct 17, 202698 ms
Oct 24, 202695 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 globalinitiative.net (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix43
  • Improve image delivery

    11.0 s · 7.3 MB

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

  • Render-blocking requests

    1.9 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.9 s.

  • Mobile performance score: 43

    43/100

    Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.4 s

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

  • Use efficient cache lifetimes

    2.6 MB

    8 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).

  • Reduce unused JavaScript

    750 ms · 145 KiB

    About 145 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Reduce unused CSS

    450 ms · 44 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Mailchimp and Google Fonts and others), adding 3.1 MB and 137 ms of main-thread time.

  • captivate.fm adds 0 ms

    0 ms

    captivate.fm costs a phone 0 ms of main-thread work and 2.6 MB 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.

  • Minify JavaScript

    150 ms · 5 KiB

    5 KiB could be saved by minifying JavaScript.

  • 3 long tasks on the main thread

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

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

    101 ms

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

Core Web Vitals

9 to fix67
  • 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.

  • Real-user CLS: 0.95

    0.95

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

  • Largest Contentful Paint: 17.9 s

    17.9 s

    Your largest element takes 17.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Cumulative Layout Shift: 0.959

    0.959

    The layout shifts by 0.959 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Time to Interactive: 17.9 s

    17.9 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Speed Index: 5.0 s

    5.0 s

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

  • 12 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

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

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

    +10%

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

4 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 101 ms

    101 ms

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Total Blocking Time: 58 ms

    58 ms

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

Images and page weight

4 to fix38
  • Page weight: 9.0 MB in 81 requests

    9.0 MB

    Your homepage downloads 9.0 MB in 81 requests on a phone: images 8.5 MB (64), scripts 317 KiB (4) and fonts 145 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 2.1 MB together. On a phone connection a single image that size takes seconds.

  • 40 images in older formats

    40 images (5.3 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.

  • 33 images below the first screen load straight away

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

  • About 2.6 g of CO₂ per visit

    2.56 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.56 g of CO₂e: 307.5 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

15 to fixGoogle 4277
  • 18 buttons without a name

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

  • Form elements must have labels (2 elements)

    Form elements must have labels: 2 elements on the page fail this check, rated critical by axe-core.

  • 8 text elements with low contrast

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

  • 8 tap targets too small

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

  • ARIA commands must have an accessible name (2 elements)

    ARIA commands must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

  • <html> element must have a valid value for the lang attribute (1 element)

    <html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 49 images without alt text

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

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

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • Zoom is disabled

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

  • 13 links without text

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

  • Page language is “en_US”

    The page declares lang=“en_US”, which is not a usable language code, so screen readers and translation tools guess.

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

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

SEO

1 to fixGoogle 9296
  • No XML sitemap

    No XML sitemap at https://globalinitiative.net/sitemap_index.xml, so Google discovers your pages only by following links.

  • 226 internal links, 21 external

    The homepage links to 226 pages on globalinitiative.net and 21 external pages.

7 checks passed
  • Meta description: 114 characters

    Your meta description is 114 characters: “Bringing people from different backgrounds together to debate and dialogue effective responses to organized crime.”.

  • One H1 headline

    Your main headline reads: “Global initiative against transnational organized crime”.

  • Title: 64 characters

    Your title is a healthy 64 characters: “Global Initiative against Transnational Organized Crime (GI-TOC)”.

  • Canonical URL set

    The canonical URL is https://globalinitiative.net/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage 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.

AI search readiness

100
  • No llms.txt

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

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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

Other pages

2 to fix70
  • 1 linked page is broken

    Your homepage links to https://globalinitiative.net/theme/sanctions-organized-crime, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 4 pages without a meta description

    https://globalinitiative.net/about-us/ypn, https://globalinitiative.net/about-us/contact, https://globalinitiative.net/about-us/awards and https://globalinitiative.net/events have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

5 checks passed
  • 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.

  • 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10078
  • 1 broken image

    1 image failed to load on a phone, for example https://globalinitiative.net/.

  • 44 small tap targets

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

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • 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 map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No opening hours

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

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

    The homepage carries about 830 words of visible text.

4 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact” and “Sign up now”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

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.

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 globalinitiative.net, 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
Analytics
Google Analytics
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on globalinitiative.net, including 18 speed issues, 1 SEO issue and 4 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