Website review, no card needed

blowplastkenya.com logo

blowplastkenya.com website review

Visit site (opens in a new tab)Reviewed 3 November 202644 issues · 92 checks

This review found 44 issues worth fixing on blowplastkenya.com, 16 of them high impact, across 92 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

Real-visitor load time (LCP)75th percentile, phones
5.8 s4.0 sMay 16Oct 314.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20265.6 s
May 23, 20265.0 s
May 30, 20264.8 s
Jun 6, 20264.4 s
Jun 13, 20264.2 s
Jun 20, 20264.4 s
Jun 27, 20264.4 s
Jul 4, 20264.7 s
Jul 11, 20265.1 s
Jul 18, 20264.9 s
Jul 25, 20264.9 s
Aug 1, 20264.9 s
Aug 8, 20264.6 s
Aug 15, 20264.5 s
Aug 22, 20264.6 s
Aug 29, 20264.7 s
Sep 5, 20264.6 s
Sep 12, 20264.6 s
Sep 19, 20264.7 s
Sep 26, 20264.6 s
Oct 3, 20264.7 s
Oct 10, 20264.7 s
Oct 17, 20264.7 s
Oct 24, 20264.7 s
Oct 31, 20264.7 s
Real-visitor tap response (INP)75th percentile, phones
121 ms78 msMay 16Oct 31104 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026111 ms
May 23, 2026111 ms
May 30, 2026109 ms
Jun 6, 2026106 ms
Jun 13, 202699 ms
Jun 20, 202699 ms
Jun 27, 2026110 ms
Jul 4, 2026110 ms
Jul 11, 2026116 ms
Jul 18, 2026115 ms
Jul 25, 2026103 ms
Aug 1, 2026103 ms
Aug 8, 2026104 ms
Aug 15, 202699 ms
Aug 22, 2026102 ms
Aug 29, 2026103 ms
Sep 5, 202694 ms
Sep 12, 202695 ms
Sep 19, 202692 ms
Sep 26, 202683 ms
Oct 3, 202692 ms
Oct 10, 202697 ms
Oct 17, 2026103 ms
Oct 24, 2026101 ms
Oct 31, 2026104 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 blowplastkenya.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. blowplastkenya.com at 1.0 s1.0 s
  2. blowplastkenya.com at 2.0 s2.0 s
  3. blowplastkenya.com at 3.0 s3.0 s
  4. blowplastkenya.com at 4.0 s4.0 s
  5. blowplastkenya.com at 5.0 s5.0 s
  6. blowplastkenya.com at 6.0 s6.0 s
  7. blowplastkenya.com at 7.0 s7.0 s
  8. blowplastkenya.com at 8.0 s8.0 s

Speed

9 to fix56
  • Render-blocking requests

    3.0 s

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

  • Reduce unused JavaScript

    900 ms · 947 KiB

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

  • Mobile performance score: 56

    56/100

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

  • Use efficient cache lifetimes

    600 ms · 240 KiB

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

  • 8 third-party services on the page

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

  • Reduce unused CSS

    360 ms · 183 KiB

    About 183 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 360 ms faster on a phone.

  • Font display

    450 ms

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

  • YouTube adds 334 ms

    334 ms

    YouTube costs a phone 334 ms of main-thread work and 978 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 Tag Manager adds 223 ms

    223 ms

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

  • Improve image delivery

    227 KiB

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

  • 6 long tasks on the main thread

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

  • Minify JavaScript

    27 KiB

    27 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    14 KiB

    Polyfills for old browsers add 14 KiB JavaScript that modern phones do not need.

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • 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: 2.0 s

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

  • Server response: 509 ms

    509 ms

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

Core Web Vitals

9 to fix67
  • 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.

  • Real-user LCP: 4.7 s

    4.7 s

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

  • Real-user FCP: 4.3 s

    4.3 s

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

  • Real-user TTFB: 2.9 s

    2.9 s

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

  • Speed Index: 13.7 s

    13.7 s

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

  • Largest Contentful Paint: 7.7 s

    7.7 s

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

  • Time to Interactive: 15.6 s

    15.6 s

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

  • First Contentful Paint: 4.1 s

    4.1 s

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

  • 20 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -8%

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

5 checks passed
  • Real-user INP: 101 ms

    101 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • Largest content (LCP) got 11% faster for real visitors

    -11%

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

  • Total Blocking Time: 177 ms

    177 ms

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

  • Cumulative Layout Shift: 0.029

    0.029

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

Images and page weight

1 to fix85
  • Page weight: 3.2 MB in 100 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 100 requests on a phone: scripts 1.7 MB (32), images 1,011 KiB (22) and stylesheets 220 KiB (26). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (75 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.

  • 1 image below the first screen load straight away

    1 image further down the page (43 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.9 g of CO₂ per visit

    0.90 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 108.2 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 7285
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Orphan list items

    Some list items are not inside a list.

  • 3 text elements with low contrast

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

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

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

  • 5 links without text

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

  • 3 form fields without a label

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 16 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

4 to fixGoogle 9283
  • Title is short (16 characters)

    Your title is only 16 characters: “Home - Blowplast”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (362 characters)

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

  • No social preview image

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

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

  • 19 internal links, 6 external

    The homepage links to 19 pages on blowplastkenya.com and 6 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Welcome to Blowplast”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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://blowplastkenya.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://blowplastkenya.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 (391 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix65
  • 3 linked pages are broken

    Your homepage links to https://blowplastkenya.com/our-ethos, https://blowplastkenya.com/news and https://blowplastkenya.com/newsletter, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 page without a meta description

    https://blowplastkenya.com/blowplast-our-team has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://blowplastkenya.com/blowplast-our-products and https://blowplastkenya.com/blowplast-contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://blowplastkenya.com/blowplast-our-products, https://blowplastkenya.com/blowplast-news and https://blowplastkenya.com/blowplast-contact-us took over 3 s to send their HTML from our server.

  • 9 internal pages checked

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

4 checks passed
  • 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

3 to fixGoogle 5085
  • 19 small tap targets

    19 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 5 third-party cookies

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Browser-reported issues

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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: 8 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 369 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Us”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

  • 5 cookies set on arrival

    5

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

  • 13 other companies contacted

    Loading the homepage contacts 13 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 blowplastkenya.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2021.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Africa (Pty) Ltd - Host Africa (Pty) Ltd

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on blowplastkenya.com, including 18 speed issues, 4 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