Website review, no card needed

synergyworldwide.com logo

synergyworldwide.com website review

Visit site (opens in a new tab)Reviewed 17 November 202639 issues · 65 checks

This review found 39 issues worth fixing on synergyworldwide.com, 21 of them high impact, across 65 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
8.7 s7.8 sMay 30Nov 148.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20268.4 s
Jun 6, 20268.5 s
Jun 13, 20268.5 s
Jun 20, 20268.5 s
Jun 27, 20268.6 s
Jul 4, 20268.5 s
Jul 11, 20268.5 s
Jul 18, 20268.4 s
Jul 25, 20268.4 s
Aug 1, 20268.6 s
Aug 8, 20268.5 s
Aug 15, 20268.5 s
Aug 22, 20268.5 s
Aug 29, 20268.3 s
Sep 5, 20268.2 s
Sep 12, 20268.1 s
Sep 19, 20267.9 s
Sep 26, 20268.0 s
Oct 3, 20268.0 s
Oct 10, 20268.1 s
Oct 17, 20268.1 s
Oct 24, 20268.0 s
Oct 31, 20268.1 s
Nov 7, 20268.2 s
Nov 14, 20268.2 s
Real-visitor tap response (INP)75th percentile, phones
395 ms363 msMay 30Nov 14385 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026374 ms
Jun 6, 2026383 ms
Jun 13, 2026384 ms
Jun 20, 2026380 ms
Jun 27, 2026382 ms
Jul 4, 2026374 ms
Jul 11, 2026374 ms
Jul 18, 2026380 ms
Jul 25, 2026378 ms
Aug 1, 2026384 ms
Aug 8, 2026391 ms
Aug 15, 2026390 ms
Aug 22, 2026387 ms
Aug 29, 2026391 ms
Sep 5, 2026384 ms
Sep 12, 2026372 ms
Sep 19, 2026371 ms
Sep 26, 2026367 ms
Oct 3, 2026370 ms
Oct 10, 2026379 ms
Oct 17, 2026377 ms
Oct 24, 2026377 ms
Oct 31, 2026372 ms
Nov 7, 2026377 ms
Nov 14, 2026385 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 synergyworldwide.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. synergyworldwide.com at 1.1 s1.1 s
  2. synergyworldwide.com at 2.2 s2.2 s
  3. synergyworldwide.com at 3.4 s3.4 s
  4. synergyworldwide.com at 4.5 s4.5 s
  5. synergyworldwide.com at 5.6 s5.6 s
  6. synergyworldwide.com at 6.7 s6.7 s
  7. synergyworldwide.com at 7.9 s7.9 s
  8. synergyworldwide.com at 9.0 s9.0 s

Speed

10 to fix3
  • Reduce unused JavaScript

    2.3 s · 2.6 MB

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

  • zoom.us adds 1.7 s

    1.7 s

    zoom.us costs a phone 1.7 s of main-thread work and 4.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Use efficient cache lifetimes

    1.0 s · 448 KiB

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

  • Main-thread work: 10.1 s

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

  • Mobile performance score: 3

    3/100

    Your mobile performance score is 3. 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 (zoom.us, Google Tag Manager and sdiapi.com and others), adding 4.7 MB and 2.0 s of main-thread time.

  • 20 long tasks on the main thread

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

  • Minify JavaScript

    420 KiB

    420 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    395 KiB

    395 KiB JavaScript is shipped twice across bundles.

  • Google Tag Manager adds 196 ms

    196 ms

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

  • Reduce unused CSS

    150 ms · 61 KiB

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

  • Render-blocking requests

    150 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

  • Legacy JavaScript

    50 KiB

    Polyfills for old browsers add 50 KiB JavaScript that modern phones do not need.

  • Improve image delivery

    15 KiB

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

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

    2 ms

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

Core Web Vitals

12 to fix0
  • 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.9 s

    9.9 s

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

  • Real-user CLS: 0.95

    0.95

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

  • Real-user FCP: 9.5 s

    9.5 s

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

  • First Contentful Paint: 7.8 s

    7.8 s

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

  • Largest Contentful Paint: 12.7 s

    12.7 s

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

  • Time to Interactive: 39.9 s

    39.9 s

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

  • Speed Index: 12.8 s

    12.8 s

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

  • Total Blocking Time: 2.6 s

    2.6 s

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

  • Cumulative Layout Shift: 0.771

    0.771

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

  • Real-user INP: 491 ms

    491 ms

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

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

Images and page weight

1 to fix33
  • Page weight: 6.3 MB in 141 requests

    6.3 MB

    Your homepage downloads 6.3 MB in 141 requests on a phone: scripts 5.4 MB (64), images 462 KiB (29) and other files 271 KiB (34). Under 2 MB keeps phones on slow connections fast.

  • About 1.8 g of CO₂ per visit

    1.80 g

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

Accessibility

Google 95100
  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 10 automated accessibility rules passed

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

SEO

8 to fixGoogle 9259
  • 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 short (17 characters)

    Your title is only 17 characters: “Synergy WorldWide”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

  • 3 links with vague text

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

  • No X (Twitter) card tag

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

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.synergyworldwide.com/ca/en-ca/sitemap.xml.

AI search readiness

1 to fix83
  • 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.synergyworldwide.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.

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

Best practices

2 to fixGoogle 7789
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://usprod.synergyworldwide.com/api/fonts' from origin 'https://www.synergyworldwide.c…”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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 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 0 words

    The homepage has only about 0 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.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 4 cookies set on arrival

    4

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

  • 1 other company contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

Framework
Angular
Hosting
Azure

Company

Founded
1999
Headquarters
Pleasant Grove

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on synergyworldwide.com, including 22 speed issues, 8 SEO issues and 5 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