Website review, no card needed

dmarcsaas.com logo

dmarcsaas.com website review

Visit site (opens in a new tab)Reviewed 9 November 202634 issues · 74 checks

This review found 34 issues worth fixing on dmarcsaas.com, 15 of them high impact, across 74 checks. The most urgent: avoid multiple page redirects. 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 dmarcsaas.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dmarcsaas.com at 0.4 s0.4 s
  2. dmarcsaas.com at 0.8 s0.8 s
  3. dmarcsaas.com at 1.1 s1.1 s
  4. dmarcsaas.com at 1.5 s1.5 s
  5. dmarcsaas.com at 1.9 s1.9 s
  6. dmarcsaas.com at 2.3 s2.3 s
  7. dmarcsaas.com at 2.6 s2.6 s
  8. dmarcsaas.com at 3.0 s3.0 s

Speed

11 to fix44
  • Avoid multiple page redirects

    29.3 s

    The page goes through 1 redirect before it starts loading, costing about 29.3 s. Link and advertise the final URL directly.

  • Reduce unused JavaScript

    7.0 s · 1.5 MB

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

  • Render-blocking requests

    5.2 s

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

  • Use efficient cache lifetimes

    1.8 s · 619 KiB

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

  • Mobile performance score: 44

    44/100

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

  • Main-thread work: 4.2 s

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

  • Improve image delivery

    2.7 MB

    16 images could be 2.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

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

  • Google Tag Manager adds 593 ms

    593 ms

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

  • Google Maps adds 133 ms

    133 ms

    Google Maps costs a phone 133 ms of main-thread work and 394 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.

  • Google CDN adds 93 ms

    93 ms

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

  • 13 long tasks on the main thread

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

  • Legacy JavaScript

    41 KiB

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

1 checks passed
  • Server response: 185 ms

    185 ms

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

Core Web Vitals

6 to fix54
  • First Contentful Paint: 12.1 s

    12.1 s

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

  • Largest Contentful Paint: 12.1 s

    12.1 s

    Your largest element takes 12.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Protect your email domains from abuse and increase your ema…”.

  • Time to Interactive: 33.9 s

    33.9 s

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

  • Speed Index: 12.1 s

    12.1 s

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

  • Total Blocking Time: 460 ms

    460 ms

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

  • 32 images without width and height

    32 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.033

    0.033

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

Images and page weight

5 to fix18
  • Page weight: 8.3 MB in 124 requests

    8.3 MB

    Your homepage downloads 8.3 MB in 124 requests on a phone: images 4.6 MB (43), scripts 2.9 MB (34) and fonts 434 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    wehkamp-pakketten.jpg weighs 847 KiB. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    886 KiB

    3 images are downloaded at several times the size a phone draws them, for example wehkamp-pakketten.jpg at 1,920 px wide, shown at 358 px. Resized copies would save about 886 KiB.

  • 3 images in older formats

    3 images (1.3 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.

  • 3 images below the first screen load straight away

    3 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.3 g of CO₂ per visit

    2.35 g

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

Accessibility

4 to fixGoogle 8994
  • 4 text elements with low contrast

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

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

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

  • 4 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

2 to fixGoogle 9288
  • No H1 headline

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

  • 3 links with vague text

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

  • 28 internal links, 3 external

    The homepage links to 28 pages on dmarcsaas.com and 3 external pages.

7 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Dé complete DMARC oplossing. Beveilig en bewaak uw e-mail domeinen eenvoudig tegen CEO fraude, phishing, impersonatie, …”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “DMARCSaaS - DMARC as a Service - DMARC Solution”.

  • Canonical URL set

    The canonical URL is https://www.dmarcsaas.com/.

  • Structured data in place

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

AI search readiness

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

    Your Organization JSON-LD is missing logo, sameAs (social profiles), 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.

  • No llms.txt

    There is no https://www.dmarcsaas.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 (400 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 2 pages share a title

    / and https://www.dmarcsaas.com/en all use the title “DMARCSaaS - DMARC as a Service - DMARC Solution”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 9 pages without a meta description

    https://www.dmarcsaas.com/waarom-dmarcsaas, https://www.dmarcsaas.com/bedreigingen, https://www.dmarcsaas.com/technieken, https://www.dmarcsaas.com/prijzen, https://www.dmarcsaas.com/de-10-meest-gemaakte-fouten-bij-het-uitrollen-van-dmarc and https://www.dmarcsaas.com/dmarc-toevoegen-is-toch-maar-een-paar-minuten-werk and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.dmarcsaas.com/en has no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.dmarcsaas.com/nieuws and https://www.dmarcsaas.com/contact 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.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 12 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 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

    8 of 9 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • Thin social proof

    Social proof on the homepage: 12 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 408 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: “PRICING”.

  • 1 call to action

    The homepage has 1 call to action, for example “Contact”.

  • 2 short forms

    2 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies, 1 of them by other companies (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.

  • 15 other companies contacted

    Loading the homepage contacts 15 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 dmarcsaas.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
Analytics
Google Tag Manager
Hosting
DigitalOcean

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on dmarcsaas.com, including 17 speed issues, 2 SEO issues and 1 conversion gap. 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