Website review, no card needed

surecomp.com logo

surecomp.com website review

Visit site (opens in a new tab)Reviewed 2 November 202646 issues · 95 checks

This review found 46 issues worth fixing on surecomp.com, 16 of them high impact, across 95 checks. The most urgent: page weight: 42.6 MB in 137 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

Real-visitor load time (LCP)75th percentile, phones
3.2 s2.1 sMay 16Oct 312.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.5 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.6 s
Jun 27, 20262.7 s
Jul 4, 20263.1 s
Jul 11, 20263.1 s
Jul 18, 20263.1 s
Jul 25, 20263.1 s
Aug 1, 20262.7 s
Aug 8, 20262.6 s
Aug 15, 20262.6 s
Aug 22, 20262.8 s
Aug 29, 20263.0 s
Sep 5, 20262.8 s
Sep 12, 20262.5 s
Sep 19, 20262.4 s
Sep 26, 20262.3 s
Oct 3, 20262.5 s
Oct 10, 20262.4 s
Oct 17, 20262.2 s
Oct 24, 20262.4 s
Oct 31, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
160 ms88 msMay 16Oct 3196 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026119 ms
May 23, 2026125 ms
May 30, 2026125 ms
Jun 6, 2026131 ms
Jun 13, 2026120 ms
Jun 20, 2026115 ms
Jun 27, 2026124 ms
Jul 4, 2026152 ms
Jul 11, 2026142 ms
Jul 18, 2026140 ms
Jul 25, 2026140 ms
Aug 1, 2026128 ms
Aug 8, 202698 ms
Aug 15, 202697 ms
Aug 22, 202698 ms
Aug 29, 2026101 ms
Sep 5, 202697 ms
Sep 12, 2026101 ms
Sep 19, 2026101 ms
Sep 26, 2026100 ms
Oct 3, 2026111 ms
Oct 10, 2026114 ms
Oct 17, 2026102 ms
Oct 24, 2026103 ms
Oct 31, 202696 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 surecomp.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. surecomp.com at 0.6 s0.6 s
  2. surecomp.com at 1.2 s1.2 s
  3. surecomp.com at 1.8 s1.8 s
  4. surecomp.com at 2.4 s2.4 s
  5. surecomp.com at 3.0 s3.0 s
  6. surecomp.com at 3.6 s3.6 s
  7. surecomp.com at 4.2 s4.2 s
  8. surecomp.com at 4.8 s4.8 s

Speed

10 to fix52
  • Improve image delivery

    2.9 s · 1.3 MB

    8 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.9 s faster on a phone.

  • Reduce unused JavaScript

    3.0 s · 594 KiB

    About 594 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.

  • Render-blocking requests

    1.1 s

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Vimeo, Google CDN and cloudflare.com and others), adding 37.2 MB and 291 ms of main-thread time.

  • Vimeo adds 142 ms

    142 ms

    Vimeo costs a phone 142 ms of main-thread work and 35.2 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.

  • Mobile performance score: 52

    52/100

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

  • Reduce unused CSS

    600 ms · 118 KiB

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

  • Main-thread work: 2.3 s

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

  • WordPress adds 0 ms

    0 ms

    WordPress costs a phone 0 ms of main-thread work and 1.6 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.

  • Google CDN adds 124 ms

    124 ms

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

  • Use efficient cache lifetimes

    150 ms · 48 KiB

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

  • Font display

    150 ms

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

  • 10 long tasks on the main thread

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

  • Minify JavaScript

    10 KiB

    10 KiB could be saved by minifying JavaScript.

  • 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

    5 KiB

    5 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

9 to fix100
  • Fails Core Web Vitals for real visitors

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

  • Largest Contentful Paint: 39.5 s

    39.5 s

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

  • Time to Interactive: 39.9 s

    39.9 s

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

  • Speed Index: 14.2 s

    14.2 s

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

  • First Contentful Paint: 3.7 s

    3.7 s

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Total Blocking Time: 265 ms

    265 ms

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

  • 9 images without width and height

    9 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) held steady for real visitors

    -4%

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

5 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 96 ms

    96 ms

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

  • Real-user CLS: 0.04

    0.04

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

  • Tap response (INP) got 18% faster for real visitors

    -18%

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

  • Cumulative Layout Shift: 0.071

    0.071

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

Images and page weight

5 to fix18
  • Page weight: 42.6 MB in 137 requests

    42.6 MB

    Your homepage downloads 42.6 MB in 137 requests on a phone: other files 36.1 MB (30), images 3.3 MB (54) and fonts 1.8 MB (17). Under 2 MB keeps phones on slow connections fast.

  • 6 images far larger than shown

    1.0 MB

    6 images are downloaded at several times the size a phone draws them, for example Best-Trade-Finance-Technology-Provider-Europe-2025_Green.png at 1,483 px wide, shown at 115 px. Resized copies would save about 1.0 MB.

  • 1 image over 500 KB

    Best-Trade-Finance-Technology-Provider-Europe-2025_Green.png weighs 499 KiB. On a phone connection a single image that size takes seconds.

  • 9 images below the first screen load straight away

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

  • 4 images in older formats

    4 images (624 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 12.1 g of CO₂ per visit

    12.09 g

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

Accessibility

11 to fixGoogle 7386
  • ARIA toggle fields must have an accessible name (3 elements)

    ARIA toggle fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 5 images without alt text

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

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

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

  • Zoom is disabled

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

  • 6 form fields without a label

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

  • 4 links without text

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

  • button, link, and menuitem elements do not have accessible names.

    button, link, and menuitem elements do not have accessible names. (1 element).

  • Headings skip levels

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

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

SEO

4 to fixGoogle 7787
  • No structured data

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

  • Meta description is long (195 characters)

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

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

  • 85 internal links, 8 external

    The homepage links to 85 pages on surecomp.com and 8 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Collaborative trade finance software”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “Trade Finance Software and Platform | Surecomp”.

  • Canonical URL set

    The canonical URL is https://surecomp.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://surecomp.com/sitemap-fc9d8150.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://surecomp.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

Other pages

2 to fix93
  • 2 pages without a meta description

    https://surecomp.com/about-us/news and https://surecomp.com/about-us/events have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://surecomp.com/rivo-for-corporates, https://surecomp.com/solutions/for-financial-institutions/rivo-for-financial-institutions and https://surecomp.com/rivo-for-fintechs 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 38 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

3 to fixGoogle 5488
  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Unexpected token ':'”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    42 of 43 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • 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.

  • About 632 words of copy

    The homepage carries about 632 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book a call” and “Contact us”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Book a call”, “Contact” and “Learn more”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 15 customer or partner logos and 22 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • 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

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 cookies, 2 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.

  • 8 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 surecomp.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 Tag Manager | Microsoft Clarity
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on surecomp.com, including 19 speed issues, 4 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