Website review, no card needed

gsw-w.com logo

gsw-w.com website review

Visit site (opens in a new tab)Reviewed 29 October 202644 issues · 76 checks

This review found 44 issues worth fixing on gsw-w.com, 21 of them high impact, across 76 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

Full-page screenshot of gsw-w.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gsw-w.com at 1.0 s1.0 s
  2. gsw-w.com at 2.0 s2.0 s
  3. gsw-w.com at 3.0 s3.0 s
  4. gsw-w.com at 4.0 s4.0 s
  5. gsw-w.com at 5.0 s5.0 s
  6. gsw-w.com at 6.0 s6.0 s
  7. gsw-w.com at 7.0 s7.0 s
  8. gsw-w.com at 8.0 s8.0 s

Speed

14 to fix38
  • Reduce unused JavaScript

    8.1 s · 1.2 MB

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

  • Render-blocking requests

    8.1 s

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

  • Use efficient cache lifetimes

    2.3 s · 427 KiB

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

  • Google Tag Manager adds 1.6 s

    1.6 s

    Google Tag Manager costs a phone 1.6 s of main-thread work and 298 KiB 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.

  • Brightcove adds 1.5 s

    1.5 s

    Brightcove costs a phone 1.5 s of main-thread work and 457 KiB 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.

  • Mobile performance score: 38

    38/100

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

  • Main-thread work: 9.5 s

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

  • 4,696 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Brightcove and Google CDN and others), adding 2.3 MB and 4.0 s of main-thread time.

  • Google CDN adds 461 ms

    461 ms

    Google CDN costs a phone 461 ms of main-thread work and 736 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.

  • Improve image delivery

    150 ms · 273 KiB

    5 images could be 273 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 81 KiB

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

  • 18 long tasks on the main thread

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

  • Vimeo adds 51 ms

    51 ms

    Vimeo costs a phone 51 ms of main-thread work and 526 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

    150 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 150 ms faster on a phone.

  • Minify JavaScript

    150 ms · 23 KiB

    23 KiB could be saved by minifying JavaScript.

  • Font display

    150 ms

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

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

    4 ms

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

Core Web Vitals

6 to fix47
  • First Contentful Paint: 11.0 s

    11.0 s

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

  • Largest Contentful Paint: 47.3 s

    47.3 s

    Your largest element takes 47.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This site uses cookies and similar tools (“Cookies”), some …”.

  • Time to Interactive: 49.8 s

    49.8 s

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

  • Speed Index: 14.5 s

    14.5 s

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

  • Total Blocking Time: 704 ms

    704 ms

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

  • 16 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0.028

    0.028

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

Images and page weight

3 to fix50
  • Page weight: 30.7 MB in 359 requests

    30.7 MB

    Your homepage downloads 30.7 MB in 359 requests on a phone: media 17.3 MB (18), images 9.5 MB (232) and scripts 2.1 MB (23). Under 2 MB keeps phones on slow connections fast.

  • 25 images in older formats

    25 images (4.8 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 far larger than shown

    257 KiB

    2 images are downloaded at several times the size a phone draws them, for example esperion-thumb.jpg at 3,200 px wide, shown at 358 px. Resized copies would save about 257 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (237 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 8.7 g of CO₂ per visit

    8.71 g

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

Accessibility

7 to fixGoogle 9290
  • 7 text elements with low contrast

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

  • Interactive controls must not be nested (6 elements)

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

  • 6 images without alt text

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

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

    All page content should be contained by landmarks: 39 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 (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.

  • Zoom is disabled

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

5 to fixGoogle 9284
  • No structured data

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

  • 3 H1 headlines

    There are 3 <h1> headlines (“Curiosity is Our Sixth Sense”, “Welcome to the WonderLab” and “The Best Ideas Begin With Wonder”). One clear main headline is easier for people and search engines.

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

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

  • No X (Twitter) card tag

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

5 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “We are a healthcare marketing agency dedicated to transforming brands through intellect, innovation, and instinct. Expl…”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “A Healthcare Marketing Agency that Transforms Brands - GSW”.

  • Canonical URL set

    The canonical URL is https://www.gsw-w.com/.

  • 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://www.gsw-w.com/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.gsw-w.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.

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

Best practices

4 to fixGoogle 5474
  • 1 broken image

    1 image failed to load on a phone, for example https://www.gsw-w.com/.

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “VIDEOJS: ERROR: (CODE:-1 undefined) [object t]”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    21 of 23 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix42
  • 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.

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

    The homepage carries about 874 words of visible text.

2 checks passed
  • 1 short form

    A short form (3 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 4 trackers load before any consent

    4

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

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies, 2 of them by other companies (measured from a US location before any click).

  • 27 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 gsw-w.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
jQuery
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on gsw-w.com, including 20 speed issues, 5 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