Website review, no card needed

kvinta.com logo

kvinta.com website review

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

This review found 34 issues worth fixing on kvinta.com, 17 of them high impact, across 76 checks. The most urgent: improve image delivery. 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 kvinta.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kvinta.com at 0.7 s0.7 s
  2. kvinta.com at 1.4 s1.4 s
  3. kvinta.com at 2.0 s2.0 s
  4. kvinta.com at 2.7 s2.7 s
  5. kvinta.com at 3.4 s3.4 s
  6. kvinta.com at 4.1 s4.1 s
  7. kvinta.com at 4.8 s4.8 s
  8. kvinta.com at 5.4 s5.4 s

Speed

8 to fix51
  • Improve image delivery

    20.3 s · 4.6 MB

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

  • Use efficient cache lifetimes

    2.6 s · 13.6 MB

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

  • Reduce unused JavaScript

    7.5 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.5 s faster on a phone.

  • Render-blocking requests

    4.5 s

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

  • Reduce unused CSS

    3.6 s · 739 KiB

    About 739 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.6 s faster on a phone.

  • Mobile performance score: 51

    51/100

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

  • 3 long tasks on the main thread

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

  • Main-thread work: 2.0 s

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Usercentrics CMP, Google Tag Manager and LinkedIn Ads and others), adding 427 KiB and 256 ms of main-thread time.

  • Legacy JavaScript

    250 ms · 40 KiB

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

  • Font display

    250 ms

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

  • 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: 197 ms

    197 ms

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

Core Web Vitals

6 to fix61
  • Largest Contentful Paint: 42.6 s

    42.6 s

    Your largest element takes 42.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This site uses third-party website tracking technologies to…”.

  • Speed Index: 17.2 s

    17.2 s

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

  • Time to Interactive: 42.8 s

    42.8 s

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

  • First Contentful Paint: 5.3 s

    5.3 s

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

  • Total Blocking Time: 260 ms

    260 ms

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

  • 17 images without width and height

    17 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

5 to fix18
  • Page weight: 41.4 MB in 77 requests

    41.4 MB

    Your homepage downloads 41.4 MB in 77 requests on a phone: media 33.1 MB (7), images 4.8 MB (28) and scripts 2.3 MB (18). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Kvinta_ws_thubnail_home-2.png weighs 3.6 MB. On a phone connection a single image that size takes seconds.

  • 7 images far larger than shown

    4.0 MB

    7 images are downloaded at several times the size a phone draws them, for example Kvinta_ws_thubnail_home-2.png at 3,000 px wide, shown at 350 px. Resized copies would save about 4.0 MB.

  • 10 images in older formats

    10 images (4.6 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.

  • 11 images below the first screen load straight away

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

  • About 11.7 g of CO₂ per visit

    11.73 g

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

Accessibility

6 to fixGoogle 8490
  • Unlabelled dropdowns

    3 dropdowns have no label.

  • 13 text elements with low contrast

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

  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

  • ARIA input fields must have an accessible name (3 elements)

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

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

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

  • 9 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

5 to fixGoogle 9279
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Kvinta | Track & Trace SaaS for Serialization & Traceability | KVINTA”.

  • No structured data

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

  • 3 H1 headlines

    There are 3 <h1> headlines (“AI-Assisted SaaS solution for Serialization and T…”, “Product portfolio spanning use-cases and industri…” and “Spezielle mobile Lösung für Lagerprozesse”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 86 internal links, 2 external

    The homepage links to 86 pages on kvinta.com and 2 external pages.

4 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Kvinta provides flexible SaaS software for product serialization, Track and Trace, regulatory compliance, warehouse ope…”.

  • Canonical URL set

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

  • 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://kvinta.com/sitemap.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://kvinta.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 (2,078 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without an H1

    https://kvinta.com/products 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 42 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 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

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

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

  • 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 1,401 words of copy

    The homepage carries about 1,401 words of visible text.

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “PHARMA START-UP Detail”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 70 testimonial or review blocks and 11 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Analytics and LinkedIn Insight.

Privacy and tracking

  • 3 trackers load before any consent

    3

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

  • 3 cookies set on arrival

    3

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

  • 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
  • Consent tool: Usercentrics

    A consent management tool (Usercentrics) 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 kvinta.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 Analytics
Hosting
IONOS

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 kvinta.com, including 14 speed issues, 5 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