Website review, no card needed

samanthayong.com logo

samanthayong.com website review

Visit site (opens in a new tab)Reviewed 17 November 202631 issues · 78 checks

This review found 31 issues worth fixing on samanthayong.com, 8 of them high impact, across 78 checks. The most urgent: reduce unused JavaScript. 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 samanthayong.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix63
  • Reduce unused JavaScript

    3.2 s · 586 KiB

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

  • Render-blocking requests

    1.3 s

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Squarespace, Google Tag Manager and sqspcdn.com and others), adding 4.0 MB and 677 ms of main-thread time.

  • Mobile performance score: 63

    63/100

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

  • Improve image delivery

    946 KiB

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

  • Squarespace adds 488 ms

    488 ms

    Squarespace costs a phone 488 ms of main-thread work and 1,010 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.

  • Reduce unused CSS

    450 ms · 87 KiB

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

  • squarespace-cdn.com adds 0 ms

    0 ms

    squarespace-cdn.com costs a phone 0 ms of main-thread work and 2.5 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.

  • 5 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 34 KiB

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

  • Use efficient cache lifetimes

    50 ms · 29 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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.

2 checks passed
  • Main-thread work: 2.0 s

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

  • Server response: 36 ms

    36 ms

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

Core Web Vitals

5 to fix63
  • Largest Contentful Paint: 13.7 s

    13.7 s

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

  • Time to Interactive: 13.8 s

    13.8 s

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

  • Speed Index: 7.3 s

    7.3 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

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

2 checks passed
  • Total Blocking Time: 159 ms

    159 ms

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

  • Cumulative Layout Shift: 0.074

    0.074

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

Images and page weight

3 to fix48
  • Page weight: 4.2 MB in 95 requests

    4.2 MB

    Your homepage downloads 4.2 MB in 95 requests on a phone: images 2.5 MB (27), scripts 1.2 MB (37) and fonts 261 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    The+Yeo+Family-29.jpg weighs 552 KiB. On a phone connection a single image that size takes seconds.

  • 3 images below the first screen load straight away

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

  • About 1.2 g of CO₂ per visit

    1.19 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 8994
  • 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.

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

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

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

  • 23 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 23 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

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

SEO

2 to fixGoogle 10089
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Samantha Yong Photography - Malaysia Children & Family Photographer”.

  • Structured data has 3 problems

    Structured data found (LocalBusiness, Organization and WebSite) but with 3 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/54cc9668e4b0710d046…”.

  • 46 internal links, 17 external

    The homepage links to 46 pages on samanthayong.com and 17 external pages.

6 checks passed
  • Meta description: 116 characters

    Your meta description is 116 characters: “Malaysia Family Photographer - Children, Maternity, Baby, and Smash Cake. Follow me on instagram @samanthayongphotos”.

  • One H1 headline

    Your main headline reads: “Let kids be”.

  • Canonical URL set

    The canonical URL is http://samanthayong.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at http://samanthayong.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing name, url, logo and description. 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://samanthayong.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 (246 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix85
  • 13 pages without a meta description

    https://samanthayong.com/about, https://samanthayong.com/contact-me, https://samanthayong.com/what-clients-say, https://samanthayong.com/malaysia-family-photographer/tag/malaysia+cake+smash, https://samanthayong.com/malaysia-family-photographer/tag/malaysia+maternity+photographer and https://samanthayong.com/malaysia-family-photographer/2023/10/7/the-millest-family and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://samanthayong.com/malaysia-family-photographer/category/Birthday%20Party, whose canonical is https://samanthayong.com/malaysia-family-photographer/category/Birthday+Party. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 12 pages without an H1

    https://samanthayong.com/malaysia-family-photographer, https://samanthayong.com/malaysia-newborn-photography, https://samanthayong.com/about, https://samanthayong.com/contact-me, https://samanthayong.com/what-clients-say and https://samanthayong.com/malaysia-family-photographer/tag/malaysia+cake+smash and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://samanthayong.com/malaysia-newborn-photography and https://samanthayong.com/contact-me 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 32 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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: the server responded with a status of 401 ()”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix83
  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 160 words

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get in Touch”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Get in Touch” and “Get In Touch”.

  • 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: 0 phone links and 1 email link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

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.

  • 5 cookies set on arrival

    5

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

  • 10 other companies contacted

    Loading the homepage contacts 10 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 samanthayong.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
Squarespace
Analytics
Google Analytics
Hosting
Squarespace

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on samanthayong.com, including 13 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