Website review, no card needed

ecuworldwide.com logo

ecuworldwide.com website review

Visit site (opens in a new tab)Reviewed 2 November 202663 issues · 87 checks

This review found 63 issues worth fixing on ecuworldwide.com, 25 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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.0 s8.6 sMay 16Oct 319.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20269.8 s
May 23, 20269.7 s
May 30, 20269.5 s
Jun 6, 20269.2 s
Jun 13, 20269.1 s
Jun 20, 20269.1 s
Jun 27, 20269.2 s
Jul 4, 20269.2 s
Jul 11, 20269.0 s
Jul 18, 20268.9 s
Jul 25, 20268.9 s
Aug 1, 20269.0 s
Aug 8, 20269.3 s
Aug 15, 20269.5 s
Aug 22, 20269.4 s
Aug 29, 20269.3 s
Sep 5, 20269.0 s
Sep 12, 20269.2 s
Sep 19, 20269.2 s
Sep 26, 20269.1 s
Oct 3, 20268.9 s
Oct 10, 20268.9 s
Oct 17, 20268.8 s
Oct 24, 20269.0 s
Oct 31, 20269.0 s
Real-visitor tap response (INP)75th percentile, phones
235 ms134 msMay 16Oct 31187 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026146 ms
May 23, 2026148 ms
May 30, 2026155 ms
Jun 6, 2026156 ms
Jun 13, 2026169 ms
Jun 20, 2026170 ms
Jun 27, 2026176 ms
Jul 4, 2026178 ms
Jul 11, 2026165 ms
Jul 18, 2026167 ms
Jul 25, 2026164 ms
Aug 1, 2026176 ms
Aug 8, 2026179 ms
Aug 15, 2026190 ms
Aug 22, 2026197 ms
Aug 29, 2026206 ms
Sep 5, 2026219 ms
Sep 12, 2026223 ms
Sep 19, 2026218 ms
Sep 26, 2026201 ms
Oct 3, 2026186 ms
Oct 10, 2026180 ms
Oct 17, 2026184 ms
Oct 24, 2026183 ms
Oct 31, 2026187 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 ecuworldwide.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ecuworldwide.com at 1.0 s1.0 s
  2. ecuworldwide.com at 2.0 s2.0 s
  3. ecuworldwide.com at 2.9 s2.9 s
  4. ecuworldwide.com at 3.9 s3.9 s
  5. ecuworldwide.com at 4.9 s4.9 s
  6. ecuworldwide.com at 5.9 s5.9 s
  7. ecuworldwide.com at 6.9 s6.9 s
  8. ecuworldwide.com at 7.8 s7.8 s

Speed

13 to fix41
  • Reduce unused JavaScript

    11.4 s · 2.3 MB

    About 2.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 11.4 s faster on a phone.

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 41

    41/100

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

  • Improve image delivery

    1.0 MB

    2 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    750 ms · 300 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Bing Ads and Google/Doubleclick Ads and others), adding 1.5 MB and 719 ms of main-thread time.

  • Legacy JavaScript

    650 ms · 54 KiB

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

  • Google Tag Manager adds 611 ms

    611 ms

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

  • Font display

    600 ms

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

  • Use efficient cache lifetimes

    300 ms · 6 KiB

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

  • 10 long tasks on the main thread

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

  • Main-thread work: 2.0 s

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

  • Bing Ads adds 102 ms

    102 ms

    Bing Ads costs a phone 102 ms of main-thread work and 581 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.

  • Document request latency

    72 KiB

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

  • Minify JavaScript

    14 KiB

    14 KiB could be saved by minifying JavaScript.

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 227 ms

    227 ms

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

Core Web Vitals

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

  • Real-user LCP: 9.7 s

    9.7 s

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

  • Real-user CLS: 0.41

    0.41

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

  • Largest Contentful Paint: 46.0 s

    46.0 s

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

  • Time to Interactive: 47.2 s

    47.2 s

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

  • Speed Index: 11.3 s

    11.3 s

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

  • Total Blocking Time: 824 ms

    824 ms

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

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

    +26%

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

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

    1.5 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • 8 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

2 checks passed
  • Real-user INP: 176 ms

    176 ms

    Real visitors wait 176 ms for the page to respond to a tap (75th percentile). 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

4 to fix25
  • Page weight: 13.9 MB in 137 requests

    13.9 MB

    Your homepage downloads 13.9 MB in 137 requests on a phone: images 7.6 MB (41), scripts 4.8 MB (45) and other files 762 KiB (29). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 5.3 MB together. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    616 KiB

    1 image is downloaded at several times the size a phone draws it, for example BannerMobImage.jpg at 1,800 px wide, shown at 390 px. Resized copies would save about 616 KiB.

  • 25 images in older formats

    25 images (7.5 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.

  • 2 images below the first screen load straight away

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

  • About 3.9 g of CO₂ per visit

    3.94 g

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

Accessibility

16 to fixGoogle 6179
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 1 button without a name

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

  • Unlabelled dropdowns

    1 dropdown has no label.

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

  • Interactive controls must not be nested (4 elements)

    Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.

  • 4 tap targets too small

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

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

  • 2 images without alt text

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

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

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

  • Heading levels should only increase by one (2 elements)

    Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

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

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

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

  • 13 form fields without a label

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

  • 10 links without text

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

  • No page language

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

9 to fixGoogle 6955
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (74 characters)

    Your title is 74 characters, so Google will cut it off around 60: “ECU Worldwide: Leading International Cargo & Air Freight Logistics Company”.

  • No structured data

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

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

  • No XML sitemap

    No XML sitemap at https://www.ecuworldwide.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at ecuworldwide.com/robots.txt, the first file search crawlers ask for.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 2 links crawlers can't follow

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

  • No X (Twitter) card tag

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

1 checks passed
  • Canonical URL set

    The canonical URL is https://www.ecuworldwide.com/.

AI search readiness

1 to fix69
  • 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.ecuworldwide.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.

Best practices

3 to fixGoogle 8885
  • 6 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured heade…”.

  • 22 distorted images

    22 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

  • Only about 126 words

    The homepage has only about 126 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get Quote”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Umami.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

  • 3 cookies set on arrival

    3

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 ecuworldwide.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
Angular
Analytics
Google Analytics | Google Tag Manager
Hosting
Azure

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 63 issues on ecuworldwide.com, including 25 speed issues, 9 SEO issues 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