Programmable

Website review, no card needed

windward.com logo

windward.com website review

Visit site (opens in a new tab)Reviewed 22 October 202628 issues · 76 checks

This review found 28 issues worth fixing on windward.com, 9 of them high impact, across 76 checks. The most urgent: render-blocking 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

Site score

77C

Closest competitors among reviewed websites

Compare side by side

One score from every part of this review. How it works

windward.com (opens in a new tab)
Full-page screenshot of windward.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. windward.com at 0.7 s0.7 s
  2. windward.com at 1.3 s1.3 s
  3. windward.com at 2.0 s2.0 s
  4. windward.com at 2.7 s2.7 s
  5. windward.com at 3.3 s3.3 s
  6. windward.com at 4.0 s4.0 s
  7. windward.com at 4.7 s4.7 s
  8. windward.com at 5.4 s5.4 s

Speed

7 to fix53

  • Render-blocking requests

    3.7 s

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

  • Reduce unused JavaScript

    870 ms · 822 KiB

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

  • Use efficient cache lifetimes

    850 ms · 529 KiB

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

  • Reduce unused CSS

    900 ms · 141 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Hubspot and Google Analytics and others), adding 1.4 MB and 864 ms of main-thread time.

  • Mobile performance score: 53

    53/100

    Your mobile performance score is 53 (desktop: 77). Pages that score under 90 lose visitors before the first paint.

  • Google Tag Manager adds 747 ms

    747 ms

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

  • 10 long tasks on the main thread

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

  • Improve image delivery

    133 KiB

    1 image could be 133 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Font display

    50 ms

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

  • Legacy JavaScript

    9 KiB

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

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

    2 KiB

    2 KiB could be saved by minifying JavaScript.

2 checks passed

  • Main-thread work: 1.8 s

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

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

6 to fix56

  • Largest Contentful Paint: 7.7 s

    7.7 s

    Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (3.6 s).

  • Time to Interactive: 16.6 s

    16.6 s

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

  • Speed Index: 6.8 s

    6.8 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Total Blocking Time: 419 ms

    419 ms

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

  • 1 image without width and height

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

    0

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

Images and page weight

1 to fix85

  • Page weight: 2.8 MB in 123 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 123 requests on a phone: scripts 1.7 MB (48), other files 370 KiB (38) and images 353 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.80 g

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

3 checks passed

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

6 to fixGoogle 9592

  • 36 text elements with low contrast

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

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails 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.

  • Headings skip levels

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

2 checks passed

  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 7 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 9298

  • 5 links with vague text

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

  • 94 internal links, 4 external

    The homepage links to 94 pages on windward.com and 4 external pages.

8 checks passed

  • Meta description: 152 characters

    Your meta description is 152 characters: “Windward helps organizations find flow in IT operations, with experience in AIOps, ITOM, ITSM & complex implementations…”.

  • One H1 headline

    Your main headline reads: “Find Flow with ServiceNow.”.

  • Title: 39 characters

    Your title is a healthy 39 characters: “IT Consulting - Find Flow with Windward”.

  • Canonical URL set

    The canonical URL is https://windward.com/.

  • 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 https://windward.com/sitemap_index.xml.

AI search readiness

100

  • No llms.txt

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

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

Other pages

4 to fix76

  • 1 page points its canonical at the homepage

    https://windward.com/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 6 pages share 2 titles

    / and https://windward.com/home all use the title “IT Consulting - Find Flow with Windward”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://windward.com/resources/ai-readiness-foundations-for-autonomous-execution and https://windward.com/resources/from-ai-assistance have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://windward.com/cmdb-optimization, https://windward.com/windward-ham-and-sam, https://windward.com/windward-service-catalog and https://windward.com/windward-multi-channel-service-desk-engagement use the same meta description. A description written for each page earns more clicks.

  • 5 pages slow to respond

    https://windward.com/case-studies, https://windward.com/windward-service-catalog, https://windward.com/windward-multi-channel-service-desk-engagement, https://windward.com/resources/ai-readiness-foundations-for-autonomous-execution and https://windward.com/resources/from-ai-assistance took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed

  • Linked pages load

    All 15 pages we checked loaded without an error.

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

Best practices

Google 100100
3 checks passed

  • No console errors

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

  • Tap targets are thumb-sized

    14 of 16 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79

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

  • About 561 words of copy

    The homepage carries about 561 words of visible text.

5 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Join Windward”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Join Windward”, “Learn More” and “learn more”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

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 LinkedIn Insight (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.

  • 8 cookies set on arrival

    8

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

  • 16 other companies contacted

    Loading the homepage contacts 16 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 windward.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 © 2024.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on windward.com, including 13 speed issues, 1 SEO issue and 2 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