Programmable

Website review, no card needed

prismamarket.ee logo

prismamarket.ee website review

Visit site (opens in a new tab)Reviewed 25 October 202626 issues · 65 checks

This review found 26 issues worth fixing on prismamarket.ee, 8 of them high impact, across 65 checks. The most urgent: use efficient cache lifetimes. 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

Site score

81B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
621 ms381 msSep 5Oct 17593 ms
Show as table
DateReal-visitor load time (LCP)
Sep 5, 2026409 ms
Sep 12, 2026471 ms
Sep 19, 2026499 ms
Sep 26, 2026512 ms
Oct 3, 2026541 ms
Oct 10, 2026572 ms
Oct 17, 2026593 ms
Real-visitor tap response (INP)75th percentile, phones
65 ms63 msSep 5Oct 1765 ms
Show as table
DateReal-visitor tap response (INP)
Sep 5, 202664 ms
Sep 12, 202663 ms
Sep 19, 202664 ms
Sep 26, 202664 ms
Oct 3, 202664 ms
Oct 10, 202665 ms
Oct 17, 202665 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

prismamarket.ee (opens in a new tab)
Full-page screenshot of prismamarket.ee (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix87

  • Use efficient cache lifetimes

    3.3 s · 1.3 MB

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

  • Improve image delivery

    2.5 s · 967 KiB

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

  • Mobile performance score: 87

    87/100

    Your mobile performance score is 87 (desktop: 97). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    700 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 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.

2 checks passed

  • Main-thread work: 0.1 s

    A phone's processor spends 0.1 s on main-thread work while loading, 16 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

4 to fix100

  • Largest Contentful Paint: 4.0 s

    4.0 s

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

  • Largest content (LCP) got 32% slower for real visitors

    +32%

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

  • Time to Interactive: 4.0 s

    4.0 s

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

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

10 checks passed

  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 0.7 s

    0.7 s

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

  • Real-user INP: 67 ms

    67 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.6 s

    0.6 s

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

  • Real-user TTFB: 289 ms

    289 ms

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

  • Speed Index: 3.0 s

    3.0 s

    Visually, the page fills in at 3.0 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.001

    0.001

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

  • First Contentful Paint: 1.0 s

    1.0 s

    The first text or image appears after 1.0 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix80

  • 5 images in older formats

    5 images (1.1 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 far larger than shown

    386 KiB

    3 images are downloaded at several times the size a phone draws them, for example Prisma_halloween_koduka_banner_900x900px.jpg at 1,200 px wide, shown at 261 px. Resized copies would save about 386 KiB.

  • 3 images below the first screen load straight away

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

  • About 0.4 g of CO₂ per visit

    0.37 g

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

1 checks passed

  • Page weight: 1.3 MB in 22 requests

    1.3 MB

    Your homepage downloads 1.3 MB in 22 requests on a phone: images 1.2 MB (11), fonts 103 KiB (3) and stylesheets 14 KiB (5). That is a lean page.

Accessibility

Google 100100
2 checks passed

  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

6 to fixGoogle 9262

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is short (12 characters)

    Your title is only 12 characters: “Prismamarket”. 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 (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

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

  • 24 internal links, 4 external

    The homepage links to 24 pages on prismamarket.ee and 4 external pages.

2 checks passed

  • 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://prismamarket.ee/wp-sitemap.xml.

AI search readiness

1 to fix83

  • 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://prismamarket.ee/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.

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

Other pages

3 to fix83

  • 5 pages share a title

    /, https://prismamarket.ee/ru, https://prismamarket.ee/soodsalt-sinule, https://prismamarket.ee/kampaania and https://prismamarket.ee/halloween all use the title “Prismamarket”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages without a meta description

    https://prismamarket.ee/leht/uudised, https://prismamarket.ee/leht/konto-teenuse-muudatus, https://prismamarket.ee/kauplused, https://prismamarket.ee/leht/kontakt, https://prismamarket.ee/leht/privaatsuspoliitika and https://prismamarket.ee/ru and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://prismamarket.ee/ru has no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 pages with very little text

    https://prismamarket.ee/leht/uudised, https://prismamarket.ee/leht/konto-teenuse-muudatus, https://prismamarket.ee/kauplused, https://prismamarket.ee/leht/kontakt, https://prismamarket.ee/ru and https://prismamarket.ee/soodsalt-sinule and 3 others 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.

  • 14 internal pages checked

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

4 checks passed

  • Linked pages load

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

    26 of 27 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix25

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • Only about 120 words

    The homepage has only about 120 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Privacy and tracking

  • 1 cookie set on arrival

    1

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

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 prismamarket.ee, 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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on prismamarket.ee, including 8 speed issues, 6 SEO issues and 6 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