Programmable

Website review, no card needed

prostudios.ke logo

prostudios.ke website review

Visit site (opens in a new tab)Reviewed 13 November 202634 issues · 74 checks

This review found 34 issues worth fixing on prostudios.ke, 15 of them high impact, across 74 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

64D

Closest competitors among reviewed websites

Compare side by side

One score from every part of this review. How it works

prostudios.ke (opens in a new tab)
Full-page screenshot of prostudios.ke (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. prostudios.ke at 0.9 s0.9 s
  2. prostudios.ke at 1.9 s1.9 s
  3. prostudios.ke at 2.8 s2.8 s
  4. prostudios.ke at 3.8 s3.8 s
  5. prostudios.ke at 4.7 s4.7 s
  6. prostudios.ke at 5.7 s5.7 s
  7. prostudios.ke at 6.6 s6.6 s
  8. prostudios.ke at 7.5 s7.5 s

Speed

9 to fix37

  • Use efficient cache lifetimes

    7.0 s · 24.5 MB

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

  • Improve image delivery

    1.2 s · 8.3 MB

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

  • Render-blocking requests

    7.0 s

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

  • Reduce unused CSS

    3.8 s · 738 KiB

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

  • Mobile performance score: 37

    37/100

    Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Reduce unused JavaScript

    150 ms · 1.9 MB

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

  • Font display

    800 ms

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Fonts and others), adding 2.4 MB and 484 ms of main-thread time.

  • Google CDN adds 437 ms

    437 ms

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

  • Document request latency

    159 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Minify CSS

    130 ms · 25 KiB

    25 KiB could be saved by minifying CSS.

  • 8 long tasks on the main thread

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

  • Legacy JavaScript

    27 KiB

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

  • Minify JavaScript

    23 KiB

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

2 checks passed

  • Main-thread work: 1.8 s

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

  • Server response: 533 ms

    533 ms

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

Core Web Vitals

5 to fix43

  • First Contentful Paint: 8.2 s

    8.2 s

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

  • Largest Contentful Paint: 10.8 s

    10.8 s

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

  • Speed Index: 16.1 s

    16.1 s

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

  • Time to Interactive: 55.7 s

    55.7 s

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

  • Cumulative Layout Shift: 0.337

    0.337

    The layout shifts by 0.337 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 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

  • Total Blocking Time: 118 ms

    118 ms

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

Images and page weight

5 to fix36

  • Page weight: 27.1 MB in 98 requests

    27.1 MB

    Your homepage downloads 27.1 MB in 98 requests on a phone: media 13.2 MB (1), images 9.5 MB (23) and scripts 3.0 MB (32). Under 2 MB keeps phones on slow connections fast.

  • 6 images over 500 KB

    6 images weigh 6.6 MB together. On a phone connection a single image that size takes seconds.

  • 19 images in older formats

    19 images (8.8 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.

  • An image on the first screen is lazy-loaded

    creative.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image far larger than shown

    137 KiB

    1 image is downloaded at several times the size a phone draws it, for example Pro-Updated.jpg at 967 px wide, shown at 120 px. Resized copies would save about 137 KiB.

  • 1 image below the first screen load straight away

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

  • About 7.7 g of CO₂ per visit

    7.69 g

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

Accessibility

5 to fix80

  • Zoom is disabled

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

  • 18 text elements with low contrast

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

  • 13 links without text

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

  • Orphan list items

    Some list items are not inside a list.

  • 5 form fields without a label

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

  • Headings skip levels

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

1 checks passed

  • Every image has alt text

    All 27 images in the HTML carry an alt attribute.

SEO

2 to fixGoogle 10087

  • No H1 headline

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

  • No social preview image

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

  • 63 internal links, 25 external

    The homepage links to 63 pages on prostudios.ke and 25 external pages.

6 checks passed

  • Meta description: 153 characters

    Your meta description is 153 characters: “Pro Studios is a top photography studio located in Nairobi 3rd Ngong Avenue. We do a variety of photo shoots such as we…”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “Pro Studios - Nairobi’s Best Photography Studio”.

  • Canonical URL set

    The canonical URL is https://prostudios.ke/.

  • Structured data in place

    Structured data found: BreadcrumbList, 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://prostudios.ke/sitemap_index.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://prostudios.ke/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 (425 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90

  • 14 pages without a meta description

    https://prostudios.ke/about-us, https://prostudios.ke/family, https://prostudios.ke/birthday, https://prostudios.ke/couple, https://prostudios.ke/product and https://prostudios.ke/baby-bump and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://prostudios.ke/about-us, https://prostudios.ke/family, https://prostudios.ke/birthday, https://prostudios.ke/couple, https://prostudios.ke/wedding-photography-and-videography and https://prostudios.ke/product and 9 others have 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 19 found) and read each the way a search engine does.

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

  • 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

2 to fixGoogle 9687

  • 9 small tap targets

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

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

1 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71

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

  • Only about 199 words

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

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

4 checks passed

  • Clear next step on the first screen

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

  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact”, “Book your shoot today” and “Get Started”.

  • 6 short forms

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

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 4 email links.

Privacy and tracking

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

  • 6 other companies contacted

    Loading the homepage contacts 6 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 prostudios.ke, 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
Hosting
Telehouse AD

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 prostudios.ke, including 14 speed issues, 2 SEO issues and 3 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