Website review, no card needed

dmt-winches.com logo

dmt-winches.com website review

Visit site (opens in a new tab)Reviewed 17 November 202643 issues · 82 checks

This review found 43 issues worth fixing on dmt-winches.com, 18 of them high impact, across 82 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

Full-page screenshot of dmt-winches.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dmt-winches.com at 2.0 s2.0 s
  2. dmt-winches.com at 4.1 s4.1 s
  3. dmt-winches.com at 6.1 s6.1 s
  4. dmt-winches.com at 8.1 s8.1 s
  5. dmt-winches.com at 10.2 s10.2 s
  6. dmt-winches.com at 12.2 s12.2 s
  7. dmt-winches.com at 14.2 s14.2 s
  8. dmt-winches.com at 16.3 s16.3 s

Speed

16 to fix34
  • Render-blocking requests

    8.2 s

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

  • Use efficient cache lifetimes

    3.1 s · 1.6 MB

    84 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).

  • Reduce unused JavaScript

    3.3 s · 1.3 MB

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

  • Font display

    3.0 s

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

  • Mobile performance score: 34

    34/100

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

  • Main-thread work: 4.5 s

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

  • 8 third-party services on the page

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

  • Google CDN adds 782 ms

    782 ms

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

  • Reduce unused CSS

    600 ms · 150 KiB

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

  • Document request latency

    650 ms

    The HTML itself could arrive about 650 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    631 ms

    Reduce initial server response time. Google estimates savings of 631 ms on a phone.

  • Improve image delivery

    300 ms · 316 KiB

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

  • Google Tag Manager adds 342 ms

    342 ms

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

  • Facebook adds 257 ms

    257 ms

    Facebook costs a phone 257 ms of main-thread work and 284 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.

  • 1,655 HTML elements

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

  • Server response: 731 ms

    731 ms

    Your server takes 731 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 19 long tasks on the main thread

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

  • Legacy JavaScript

    50 ms · 51 KiB

    Polyfills for old browsers add 51 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

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

    4 KiB

    4 KiB could be saved by minifying CSS.

Core Web Vitals

6 to fix43
  • Largest Contentful Paint: 16.5 s

    16.5 s

    Your largest element takes 16.5 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 (12.2 s).

  • Speed Index: 26.6 s

    26.6 s

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

  • Time to Interactive: 25.1 s

    25.1 s

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

  • First Contentful Paint: 6.8 s

    6.8 s

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

  • Total Blocking Time: 877 ms

    877 ms

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

  • 2 images without width and height

    2 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.064

    0.064

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

Images and page weight

3 to fix53
  • Page weight: 4.3 MB in 146 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 146 requests on a phone: scripts 2.4 MB (56), images 743 KiB (18) and other files 728 KiB (26). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Production-Plant-768x461.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 7 images in older formats

    7 images (508 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.

  • About 1.2 g of CO₂ per visit

    1.23 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.23 g of CO₂e: 147.4 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

7 to fixGoogle 8490
  • 9 text elements with low contrast

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • Zoom is disabled

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

  • 12 links without text

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 37 automated accessibility rules passed

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

SEO

4 to fixGoogle 7784
  • No H1 headline

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

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

  • 154 internal links, 7 external

    The homepage links to 154 pages on dmt-winches.com and 7 external pages.

6 checks passed
  • Meta description: 126 characters

    Your meta description is 126 characters: “DMT is a leading and competitive supplier, specialized in designing and manufacturing marine winches and other deck mac…”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Winches and other deck machinery - You name it, we build it!”.

  • Canonical URL set

    The canonical URL is https://www.dmt-winches.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage and WebSite.

  • 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.dmt-winches.com/sitemap_index.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://dmt-winches.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 (850 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 15 pages without an H1

    https://dmt-winches.com/general-terms-and-conditions, https://dmt-winches.com/policies-and-regulations, https://dmt-winches.com/products, https://dmt-winches.com/winches, https://dmt-winches.com/anchor-winches and https://dmt-winches.com/anchor-handling-winches and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://dmt-winches.com/general-terms-and-conditions, https://dmt-winches.com/policies-and-regulations, https://dmt-winches.com/products and https://dmt-winches.com/winches took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

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

Best practices

1 to fixGoogle 6993
  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://dmt-winches.com/' was loaded over HTTPS, but requested an insecure font 'http://www…”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    10 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • About 551 words of copy

    The homepage carries about 551 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and LinkedIn Insight.

Privacy and tracking

  • 6 trackers load before any consent

    6

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

  • 9 cookies set on arrival

    9

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

  • 26 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 dmt-winches.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Vodafone Romania S.A.

Hiring

Hiring
17 open roles
Job board
careers page

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on dmt-winches.com, including 22 speed issues, 4 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