Website review, no card needed

exchangegateway.org logo

exchangegateway.org website review

Visit site (opens in a new tab)Reviewed 20 November 202635 issues · 82 checks

This review found 35 issues worth fixing on exchangegateway.org, 14 of them high impact, across 82 checks. The most urgent: page weight: 29.5 MB in 94 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
10.9 s5.7 sMay 30Nov 1410.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20266.4 s
Jun 6, 20266.5 s
Jun 13, 20266.3 s
Jun 20, 20266.3 s
Nov 7, 20269.8 s
Nov 14, 202610.3 s
Real-visitor tap response (INP)75th percentile, phones
446 ms283 msMay 30Jun 20427 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026302 ms
Jun 6, 2026307 ms
Jun 13, 2026336 ms
Jun 20, 2026427 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 exchangegateway.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. exchangegateway.org at 1.6 s1.6 s
  2. exchangegateway.org at 3.1 s3.1 s
  3. exchangegateway.org at 4.7 s4.7 s
  4. exchangegateway.org at 6.2 s6.2 s
  5. exchangegateway.org at 7.8 s7.8 s
  6. exchangegateway.org at 9.3 s9.3 s
  7. exchangegateway.org at 10.9 s10.9 s
  8. exchangegateway.org at 12.4 s12.4 s

Speed

8 to fix62
  • Render-blocking requests

    2.9 s

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

  • Font display

    1.3 s

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

  • Improve image delivery

    450 ms · 19.3 MB

    30 images could be 19.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. 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, Google Fonts and eflowsys.com and others), adding 13.5 MB and 81 ms of main-thread time.

  • eflowsys.com adds 0 ms

    0 ms

    eflowsys.com costs a phone 0 ms of main-thread work and 13.3 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.

  • Mobile performance score: 62

    62/100

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

  • Reduce unused JavaScript

    450 ms · 103 KiB

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

  • 1,794 HTML elements

    The page has 1,794 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 3 long tasks on the main thread

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

  • Reduce unused CSS

    20 ms · 27 KiB

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

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.7 s

    A phone's processor spends 1.7 s on main-thread work while loading, 561 ms of it running JavaScript. That is comfortably low.

  • Server response: 445 ms

    445 ms

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

Core Web Vitals

10 to fix50
  • 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 LCP: 10.3 s

    10.3 s

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

  • Real-user FCP: 5.2 s

    5.2 s

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

  • Real-user TTFB: 2.9 s

    2.9 s

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

  • Speed Index: 16.2 s

    16.2 s

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

  • Largest Contentful Paint: 8.4 s

    8.4 s

    Your largest element takes 8.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Product & Service Previous e-Signing Doc Platform Learn mor…”. Most of its time is resource load delay (5.9 s).

  • Time to Interactive: 10.2 s

    10.2 s

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

  • Tap response (INP) got 25% slower for real visitors

    +25%

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

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

    +57%

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

3 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Total Blocking Time: 118 ms

    118 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 29.5 MB in 94 requests

    29.5 MB

    Your homepage downloads 29.5 MB in 94 requests on a phone: images 28.8 MB (42), scripts 356 KiB (26) and fonts 117 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (31 KiB) is 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.

  • About 8.3 g of CO₂ per visit

    8.35 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9094
  • 5 text elements with low contrast

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

  • 3 tap targets too small

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

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

  • 3 links without text

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

2 checks passed
  • Every image has alt text

    All 54 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

3 to fixGoogle 8591
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Enterprise Exchange gateway Electronic Data Inter…”). One clear main headline is easier for people and search engines.

  • 10 links with vague text

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 67 internal links, 12 external

    The homepage links to 67 pages on exchangegateway.org and 12 external pages.

7 checks passed
  • Meta description: 132 characters

    Your meta description is 132 characters: “Exchange Gateway SaaS RPA 100%, Data Corrector + Validation, Convertor, Alert Notice, Transaction Log, Routing I/O with…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Exchange Gateway Electronic Data Interchange Turn Key Solution”.

  • Canonical URL set

    The canonical URL is https://exchangegateway.org/.

  • Structured data in place

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

  • XML sitemap found

    Your XML sitemap is reachable at http://exchangegateway.org/sitemap_index.xml.

AI search readiness

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

Other pages

5 to fix50
  • 1 linked page is broken

    Your homepage links to https://exchangegateway.org/exchange-gateway-platform, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 4 pages without a title

    https://exchangegateway.org/e-tax-engine-solution-01, https://exchangegateway.org/e-tax-engine-solution-02, https://exchangegateway.org/e-tax-engine-solution-03 and https://exchangegateway.org/eflowsys-event-0003 have no <title>, so Google invents the link text in results.

  • 6 pages without a meta description

    https://exchangegateway.org/under-construction, https://exchangegateway.org/contact-us, https://exchangegateway.org/e-tax-engine-solution-01, https://exchangegateway.org/e-tax-engine-solution-02, https://exchangegateway.org/e-tax-engine-solution-03 and https://exchangegateway.org/eflowsys-event-0003 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://exchangegateway.org/edi-data-exchange-gateway and https://exchangegateway.org/data-exchange use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://exchangegateway.org/contact-us, https://exchangegateway.org/e-tax-engine-solution-01, https://exchangegateway.org/e-tax-engine-solution-02, https://exchangegateway.org/e-tax-engine-solution-03 and https://exchangegateway.org/eflowsys-event-0003 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages slow to respond

    https://exchangegateway.org/edi-data-exchange-gateway, https://exchangegateway.org/e-tax-engine-platform, https://exchangegateway.org/under-construction, https://exchangegateway.org/e-tax-engine-solution-01, https://exchangegateway.org/e-tax-engine-solution-02 and https://exchangegateway.org/e-tax-engine-solution-03 and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 7387
  • 25 small tap targets

    25 of 44 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 “callCookieList is not defined”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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 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 818 words of copy

    The homepage carries about 818 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact us” and “Learn more”.

  • Social proof on the page

    Social proof on the homepage: 30 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads 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.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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 exchangegateway.org, 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
National Telecom Public Company Limited

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on exchangegateway.org, including 18 speed issues, 3 SEO issues and 1 conversion gap. 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