Website review, no card needed

capturememories.in logo

capturememories.in website review

Visit site (opens in a new tab)Reviewed 21 November 202632 issues · 77 checks

This review found 32 issues worth fixing on capturememories.in, 11 of them high impact, across 77 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

Full-page screenshot of capturememories.in (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix59
  • Render-blocking requests

    3.0 s

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

  • Reduce unused JavaScript

    2.4 s · 465 KiB

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

  • Mobile performance score: 59

    59/100

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

  • Use efficient cache lifetimes

    750 ms · 179 KiB

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

  • Reduce unused CSS

    380 ms · 100 KiB

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

  • Google Tag Manager adds 374 ms

    374 ms

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

  • Font display

    350 ms

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 671 KiB and 376 ms of main-thread time.

  • Improve image delivery

    163 KiB

    3 images could be 163 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 137 ms. During a long task the page ignores taps.

  • Minify JavaScript

    80 ms · 5 KiB

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.4 s

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

  • Server response: 39 ms

    39 ms

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

Core Web Vitals

6 to fix63
  • Largest Contentful Paint: 9.0 s

    9.0 s

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Time to Interactive: 9.0 s

    9.0 s

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

  • Speed Index: 6.5 s

    6.5 s

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

  • Total Blocking Time: 215 ms

    215 ms

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

  • 1 image without width and height

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

1 to fix90
  • 1 image far larger than shown

    57 KiB

    1 image is downloaded at several times the size a phone draws it, for example Engagement-1-scaled.jpg at 800 px wide, shown at 187 px. Resized copies would save about 57 KiB.

  • About 0.5 g of CO₂ per visit

    0.47 g

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

3 checks passed
  • Page weight: 1.7 MB in 77 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 77 requests on a phone: scripts 982 KiB (29), images 309 KiB (14) and fonts 223 KiB (7). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

9 to fixGoogle 5782
  • 11 text elements with low contrast

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 8 images without alt text

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

  • No main landmark

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

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 6 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 25 automated accessibility rules passed

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

SEO

4 to fixGoogle 9285
  • Meta description is short (44 characters)

    Your meta description is only 44 characters: “BeFlower | Best WordPress theme for florists”. 70 to 160 characters is enough to sell the click.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Home” and “Our Services”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, 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.

  • 21 internal links, 4 external

    The homepage links to 21 pages on capturememories.in and 4 external pages.

5 checks passed
  • Title: 51 characters

    Your title is a healthy 51 characters: “Capture Memories - Wedding and Newborn Photographer”.

  • Canonical URL set

    The canonical URL is https://capturememories.in/.

  • Structured data in place

    Structured data found: WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://capturememories.in/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://capturememories.in/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 (281 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix98
  • 11 pages share a meta description

    https://capturememories.in/about, https://capturememories.in/contact, https://capturememories.in/faq, https://capturememories.in/gallery, https://capturememories.in/gallery/weddings and https://capturememories.in/portfolio-item/babies and 5 others use the same meta description. A description written for each page earns more clicks.

  • 6 pages with very little text

    https://capturememories.in/gallery/weddings, https://capturememories.in/portfolio-item/babies, https://capturememories.in/portfolio-item/family-shoot, https://capturememories.in/gallery/pre-wedding, https://capturememories.in/portfolio-item/maternity and https://capturememories.in/portfolio 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.

  • 11 internal pages checked

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

7 checks passed
  • Linked pages load

    All 11 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 11 pages that loaded have a meta description.

  • 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 11 pages that loaded have a <title>.

Best practices

Google 100100
2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

    The homepage carries about 265 words of visible text.

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies (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.

  • 4 other companies contacted

    Loading the homepage contacts 4 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 capturememories.in, 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 © 2020.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Hostinger

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on capturememories.in, including 13 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