Website review, no card needed

denwiss.com logo

denwiss.com website review

Visit site (opens in a new tab)Reviewed 8 November 202624 issues · 72 checks

This review found 24 issues worth fixing on denwiss.com, 5 of them high impact, across 72 checks. The most urgent: scrollable region must have keyboard access (1 element). 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 denwiss.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. denwiss.com at 0.7 s0.7 s
  2. denwiss.com at 1.4 s1.4 s
  3. denwiss.com at 2.1 s2.1 s
  4. denwiss.com at 2.8 s2.8 s
  5. denwiss.com at 3.5 s3.5 s
  6. denwiss.com at 4.2 s4.2 s
  7. denwiss.com at 4.9 s4.9 s
  8. denwiss.com at 5.6 s5.6 s

Speed

3 to fix86
  • Mobile performance score: 86

    86/100

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

  • Render-blocking requests

    500 ms

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

  • 1,507 HTML elements

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

  • Improve image delivery

    150 ms · 27 KiB

    2 images could be 27 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.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Shopify and shop.app), adding 251 KiB and 23 ms of main-thread time.

  • Reduce unused JavaScript

    10 ms · 27 KiB

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

  • Reduce unused CSS

    10 KiB

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

  • Use efficient cache lifetimes

    6 KiB

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

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

    4 KiB

    4 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    3 KiB

    3 KiB JavaScript is shipped twice across bundles.

2 checks passed
  • Main-thread work: 2.0 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

2 to fix86
  • Largest Contentful Paint: 3.7 s

    3.7 s

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

  • Speed Index: 4.7 s

    4.7 s

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

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

4 checks passed
  • Time to Interactive: 3.7 s

    3.7 s

    The page is fully interactive after 3.7 s.

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0.004

    0.004

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.46 g

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

4 checks passed
  • Page weight: 1.6 MB in 228 requests

    1.6 MB

    Your homepage downloads 1.6 MB in 228 requests on a phone: other files 840 KiB (115), scripts 308 KiB (58) and images 261 KiB (33). That is a lean page.

  • 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 9593
  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • Summary elements must have discernible text (1 element)

    Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 6 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 31 images in the HTML carry an alt attribute.

  • 48 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: 48 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

4 to fixGoogle 9276
  • No H1 headline

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

  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “The most cost-effective supplier of dental lab consumables – Wissden”.

  • Meta description is long (223 characters)

    Your meta description is 223 characters; Google truncates after about 160, so the end of your pitch is cut.

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

  • 125 internal links, 7 external

    The homepage links to 125 pages on denwiss.com and 7 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization 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://denwiss.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

  • llms.txt published

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

Other pages

4 to fix73
  • 1 page points its canonical at the homepage

    https://denwiss.com/products/wissden-press-rod-investment-ring-alox-plunger100g-200g 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.

  • 2 pages share a title

    / and https://denwiss.com/products/wissden-press-rod-investment-ring-alox-plunger100g-200g all use the title “The most cost-effective supplier of dental lab consumables – Wissden”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages without a meta description

    https://denwiss.com/collections/ht, https://denwiss.com/collections/stc, https://denwiss.com/collections/stml, https://denwiss.com/collections/3d, https://denwiss.com/collections/4d and https://denwiss.com/collections/ngz-multilayer-zirconia and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://denwiss.com/products/wissden-press-rod-investment-ring-alox-plunger100g-200g has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

1 to fixGoogle 9693
  • 6 small tap targets

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

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • About 906 words of copy

    The homepage carries about 906 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “START SHOPPING”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact Us”, “Order Tracking” and “Contact us”.

  • 5 short forms

    5 short forms (2 fields at most) are right on the homepage.

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

  • 9 cookies set on arrival

    9

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

  • 9 other companies contacted

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

Apps on your store

No apps were seen in the code your storefront loads.

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

Stack

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 24 issues on denwiss.com, including 5 speed issues, 4 SEO issues 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