Website review, no card needed

knightweave.com logo

knightweave.com website review

Visit site (opens in a new tab)Reviewed 9 November 202625 issues · 100 checks

This review found 25 issues worth fixing on knightweave.com, 9 of them high impact, across 100 checks. The most urgent: main-thread work: 4.3 s. 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
1.6 s833 msMay 23Nov 7932 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.2 s
Oct 10, 20261.0 s
Oct 17, 2026976 ms
Oct 24, 2026940 ms
Oct 31, 2026921 ms
Nov 7, 2026932 ms
Real-visitor tap response (INP)75th percentile, phones
166 ms123 msMay 23Nov 7128 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026132 ms
May 30, 2026138 ms
Jun 6, 2026147 ms
Jun 13, 2026153 ms
Jun 20, 2026153 ms
Jun 27, 2026154 ms
Jul 4, 2026154 ms
Jul 11, 2026154 ms
Jul 18, 2026155 ms
Jul 25, 2026160 ms
Aug 1, 2026161 ms
Aug 8, 2026160 ms
Aug 15, 2026155 ms
Aug 22, 2026154 ms
Aug 29, 2026154 ms
Sep 5, 2026155 ms
Sep 12, 2026158 ms
Sep 19, 2026161 ms
Sep 26, 2026161 ms
Oct 3, 2026146 ms
Oct 10, 2026137 ms
Oct 17, 2026132 ms
Oct 24, 2026129 ms
Oct 31, 2026128 ms
Nov 7, 2026128 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 knightweave.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. knightweave.com at 0.7 s0.7 s
  2. knightweave.com at 1.5 s1.5 s
  3. knightweave.com at 2.2 s2.2 s
  4. knightweave.com at 2.9 s2.9 s
  5. knightweave.com at 3.6 s3.6 s
  6. knightweave.com at 4.4 s4.4 s
  7. knightweave.com at 5.1 s5.1 s
  8. knightweave.com at 5.8 s5.8 s

knightweave.com does not allow embedding, so this is Google's rendering of the page.

Speed

6 to fix80
  • Main-thread work: 4.3 s

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

  • 3,083 HTML elements

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

  • Mobile performance score: 80

    80/100

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

  • Render-blocking requests

    800 ms

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

  • Reduce unused JavaScript

    300 ms · 90 KiB

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

  • Shopify adds 162 ms

    162 ms

    Shopify costs a phone 162 ms of main-thread work and 698 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.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Shopify, Klaviyo and shop.app and others), adding 1,022 KiB and 266 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Use efficient cache lifetimes

    49 KiB

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

  • Improve image delivery

    48 KiB

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

  • Reduce unused CSS

    27 KiB

    About 27 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 17 ms

    17 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 4.9 s

    4.9 s

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

  • Time to Interactive: 7.7 s

    7.7 s

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

  • Speed Index: 4.0 s

    4.0 s

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

  • Tap response (INP) held steady for real visitors

    -5%

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

10 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.1 s

    1.1 s

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

  • Real-user INP: 124 ms

    124 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 465 ms

    465 ms

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

  • Largest content (LCP) got 38% faster for real visitors

    -38%

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.01

    0.01

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

  • Total Blocking Time: 39 ms

    39 ms

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

Images and page weight

1 to fix85
  • Page weight: 3.0 MB in 392 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 392 requests on a phone: other files 1.1 MB (184), scripts 938 KiB (167) and images 513 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 4 images in older formats

    4 images (229 KiB) 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.

  • 1 image below the first screen load straight away

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

  • About 0.9 g of CO₂ per visit

    0.85 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

5 to fixGoogle 9493
  • Elements must only use permitted ARIA attributes (29 elements)

    Elements must only use permitted ARIA attributes: 29 elements on the page fail this check, rated serious by axe-core.

  • 2 text elements with low contrast

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

  • 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 (3 elements)

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

  • 4 links without text

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

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

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 52 automated accessibility rules passed

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

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

  • 134 internal links, 5 external

    The homepage links to 134 pages on knightweave.com and 5 external pages.

7 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “Shop functional fantasy cloaks built for warmth, comfort and adventure. Find durable ranger cloaks, hooded capes and me…”.

  • One H1 headline

    Your main headline reads: “Knightweave”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Knightweave | Functional Fantasy-Style Cloaks”.

  • Canonical URL set

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

  • 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://knightweave.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.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,079 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes /llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 1 page without a meta description

    /collections/tees has no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    /products/cloak-for-adult, /products/scout-cloak, /products/sun-cloak, /products/royal-collection, /products/windskin and /products/air-tunic and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages with very little text

    /products/cloak-for-adult, /products/scout-cloak, /products/sun-cloak, /products/royal-collection, /products/windskin and /products/air-tunic and 2 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    13 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “fbq is not defined”.

2 checks passed
  • Tap targets are thumb-sized

    26 of 31 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

1 to fix86
  • 1 broken link to your own pages

    1 link from your homepage to your own site is broken, for example https://knightweave.com/products/dustcoat-signature (network).

  • Short HSTS lifetime

    HSTS is set, but max-age is 91 days; one year is the recommended minimum.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

6 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (knightweave.com).

  • Valid certificate (64 days left)

    The certificate from Let's Encrypt · YE2 verifies for knightweave.com and is valid for another 64 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://knightweave.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

Domain and trust

1 to fix
  • Domain expires in 76 days

    knightweave.com is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.

  • No CAA record

    knightweave.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

  • DNSSEC is off

    knightweave.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

1 checks passed
  • Domain is 2 years old

    2 years

    knightweave.com was registered in Jan 2024 through Tucows Domains Inc.. An established domain carries more trust with email providers and search engines.

Content and conversion

2 to fix75
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 585 words of visible text.

4 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact Us”, “SHOP CLOAKS” and “Shop all products”.

  • 29 short forms

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

  • Social proof on the page

    Social proof on the homepage: 18 testimonial or review blocks, a star rating and 2 trust badges.

  • Direct contact links

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

Email authentication

95
  • Email authentication score: 95/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed
  • DMARC policy: reject

    DMARC tells receivers to reject mail that fails authentication.

  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:_spf.google.com ~all”.

  • DKIM signing found

    A DKIM key is published (selector “google”), so receivers can verify mail really came from you.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 18 cookies set on arrival

    18

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

  • 31 other companies contacted

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

Apps on your store

Your storefront loads 7 apps. Each one is code from another company running for your shoppers.

None of the apps your storefront loads is on the list of apps with a known security problem.

Apps your storefront loads

Gsc Product Labels Badges · Klaviyo Email Marketing Sms · Hulk Form Builder · Judge Me Reviews · Fbp Fast Bundle · Gsc Affiliate External Links · bogos.io

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on knightweave.com, including 9 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