Website review, no card needed

4comply.io logo

4comply.io website review

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

This review found 43 issues worth fixing on 4comply.io, 11 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 4comply.io (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 4comply.io at 1.7 s1.7 s
  2. 4comply.io at 3.3 s3.3 s
  3. 4comply.io at 5.0 s5.0 s
  4. 4comply.io at 6.7 s6.7 s
  5. 4comply.io at 8.3 s8.3 s
  6. 4comply.io at 10.0 s10.0 s
  7. 4comply.io at 11.7 s11.7 s
  8. 4comply.io at 13.3 s13.3 s

Speed

7 to fix74
  • Render-blocking requests

    1.8 s

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

  • Mobile performance score: 74

    74/100

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

  • Reduce unused CSS

    600 ms · 123 KiB

    About 123 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, LinkedIn Ads and Cloudflare and others), adding 637 KiB and 514 ms of main-thread time.

  • Google Tag Manager adds 481 ms

    481 ms

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

  • Reduce unused JavaScript

    150 ms · 319 KiB

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

  • Main-thread work: 3.6 s

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

  • 5 long tasks on the main thread

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

  • Improve image delivery

    111 KiB

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

  • Use efficient cache lifetimes

    14 KiB

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

  • Minify JavaScript

    13 KiB

    13 KiB could be saved by minifying JavaScript.

  • Minify CSS

    12 KiB

    12 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    10 KiB

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

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

6 to fix86
  • Speed Index: 15.2 s

    15.2 s

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

  • Time to Interactive: 10.7 s

    10.7 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Total Blocking Time: 351 ms

    351 ms

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

  • Largest Contentful Paint: 2.7 s

    2.7 s

    Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “4Comply SaaS Software to Maximize Growth while Ensuring Pri…”. Most of its time is element render delay (2.3 s).

  • 12 images without width and height

    12 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

    0

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

Images and page weight

1 to fix70
  • Page weight: 4.6 MB in 92 requests

    4.6 MB

    Your homepage downloads 4.6 MB in 92 requests on a phone: images 3.4 MB (24), scripts 857 KiB (26) and fonts 178 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 6 images in older formats

    6 images (351 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.

  • 4 images below the first screen load straight away

    4 images further down the page (179 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.3 g of CO₂ per visit

    1.30 g

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

11 to fixGoogle 6082
  • 8 text elements with low contrast

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

  • Links look like plain text

    2 links inside paragraphs rely on colour alone to stand out.

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

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

    Main 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 main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Zoom is disabled

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

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

  • 2 form fields without a label

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

  • 2 links without text

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

  • Headings skip levels

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

1 checks passed
  • 31 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: 31 passed and 11 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

8 to fixGoogle 5048
  • Page is set to noindex

    The robots meta tag says “nofollow, noindex”: Google is told not to list this page at all.

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Title is short (26 characters)

    Your title is only 26 characters: “4Comply Privacy Compliance”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

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

  • No XML sitemap

    No XML sitemap at https://4comply.io/sitemap.xml, so Google discovers your pages only by following links.

  • 13 links with vague text

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

  • 73 internal links, 9 external

    The homepage links to 73 pages on 4comply.io and 9 external pages.

3 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “The 4Comply is a SaaS privacy solution for managing consent and rights requests across your organization. Supports GDPR…”.

  • One H1 headline

    Your main headline reads: “Home”.

  • robots.txt in place

    robots.txt is in place.

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://4comply.io/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 (430 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix79
  • 11 linked pages hidden from search

    https://4comply.io/4comply-services-training-options, https://4comply.io/developers, https://4comply.io/articles, https://4comply.io/resources, https://4comply.io/contact-us and https://4comply.io/pricing and 5 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://4comply.io/4comply-services-training-options and https://4comply.io/services all use the title “4Comply Services and Training Options from 4Thought Marketing”. 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://4comply.io/resources and https://4comply.io/contact-us have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://4comply.io/4comply-services-training-options and https://4comply.io/services use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 17 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.

  • Canonical URLs point to themselves

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

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9289
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “The Content-Security-Policy directive name 'Strict-Transport-Security:' contains one or more invalid characters. Only A…”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

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.

  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. 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 294 words of copy

    The homepage carries about 294 words of visible text.

4 checks passed
  • 11 calls to action

    The homepage has 11 calls to action, for example “Contact Us”, “Pricing” 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 Cloudflare Web Analytics.

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

  • 7 cookies set on arrival

    7

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 4comply.io, 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 Tag Manager
Hosting
Cloudflare

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 4comply.io, including 13 speed issues, 8 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