Website review, no card needed

samuelsabandar.com logo

samuelsabandar.com website review

Visit site (opens in a new tab)Reviewed 17 November 202625 issues · 73 checks

This review found 25 issues worth fixing on samuelsabandar.com, 11 of them high impact, across 73 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 samuelsabandar.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. samuelsabandar.com at 0.6 s0.6 s
  2. samuelsabandar.com at 1.1 s1.1 s
  3. samuelsabandar.com at 1.7 s1.7 s
  4. samuelsabandar.com at 2.2 s2.2 s
  5. samuelsabandar.com at 2.8 s2.8 s
  6. samuelsabandar.com at 3.3 s3.3 s
  7. samuelsabandar.com at 3.9 s3.9 s
  8. samuelsabandar.com at 4.4 s4.4 s

Speed

7 to fix57
  • Reduce unused JavaScript

    1.8 s · 434 KiB

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

  • Use efficient cache lifetimes

    1.8 s · 231 KiB

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

  • Mobile performance score: 57

    57/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google CDN and Facebook and others), adding 1.0 MB and 511 ms of main-thread time.

  • Render-blocking requests

    300 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

  • Shopify adds 181 ms

    181 ms

    Shopify costs a phone 181 ms of main-thread work and 465 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 CDN adds 170 ms

    170 ms

    Google CDN costs a phone 170 ms of main-thread work and 329 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

    180 ms · 61 KiB

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

  • Duplicated JavaScript

    150 ms · 5 KiB

    5 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • 5 long tasks on the main thread

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

  • Improve image delivery

    58 KiB

    1 image could be 58 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    11 KiB

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

  • Minify JavaScript

    9 KiB

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.7 s

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

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

6 to fix60
  • Largest Contentful Paint: 10.4 s

    10.4 s

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

  • Time to Interactive: 11.5 s

    11.5 s

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

  • First Contentful Paint: 3.4 s

    3.4 s

    The first text or image appears after 3.4 s on a phone. Good is under 1.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: 284 ms

    284 ms

    Scripts block taps and scrolling for 284 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 fix85
  • Page weight: 2.6 MB in 151 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 151 requests on a phone: scripts 1.1 MB (46), other files 703 KiB (85) and images 538 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.74 g

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

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

  • Images are sized for phones

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

Accessibility

3 to fixGoogle 9193
  • [role="img"] and [role="image"] elements must have alternative text (2 elements)

    [role="img"] and [role="image"] elements must have alternative text: 2 elements on the page fail this check, rated serious by axe-core.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • Headings skip levels

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

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

1 to fixGoogle 9295
  • Meta description is long (180 characters)

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

  • 19 internal links, 8 external

    The homepage links to 19 pages on samuelsabandar.com and 8 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “SHOPIFY EXPERT OF INDONESIA”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “SSDC | Indonesia Shopify Expert & Web Developer”.

  • Canonical URL set

    The canonical URL is https://ssdc.co/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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 https://ssdc.co/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (323 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://ssdc.co/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix93
  • 2 pages share a meta description

    https://ssdc.co/blogs/projects and https://ssdc.co/blogs/news use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://ssdc.co/pages/about-us, https://ssdc.co/blogs/projects, https://ssdc.co/pages/pricing and https://ssdc.co/pages/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 internal pages checked

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

6 checks passed
  • Linked pages load

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

  • 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

2 to fixGoogle 10087
  • 2 small tap targets

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

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix60
  • 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.

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

    The homepage carries about 261 words of visible text.

3 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Pricing”, “Contact” and “Learn more about Us”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Meta Pixel.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 9 cookies set on arrival

    9

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

  • 17 other companies contacted

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

Apps on your store

Your storefront loads 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Powerful Form Builder · Google Youtube · Hulk Contact Form Builder · Whatsapp Chat Button · Ecomsend · hulkapps.com · Hulk Product Options

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Bootstrap
E-commerce
Shopify
Hosting
Shopify

Hiring

Hiring
1 open role
Job board
careers page

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on samuelsabandar.com, including 13 speed issues, 1 SEO issue 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