Website review, no card needed

unitagstore.com logo

unitagstore.com website review

Visit site (opens in a new tab)Reviewed 20 October 202629 issues · 79 checks

This review found 29 issues worth fixing on unitagstore.com, 7 of them high impact, across 79 checks. The most urgent: fails Core Web Vitals for real visitors. 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
7.3 s2.1 sMay 2Oct 173.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20266.0 s
May 9, 20266.1 s
May 16, 20266.5 s
May 23, 20266.6 s
May 30, 20266.6 s
Jun 6, 20266.7 s
Jun 13, 20266.7 s
Jun 20, 20266.4 s
Jun 27, 20266.3 s
Jul 4, 20266.2 s
Jul 11, 20266.1 s
Jul 18, 20266.2 s
Jul 25, 20266.3 s
Aug 1, 20266.4 s
Aug 8, 20266.3 s
Aug 22, 20265.9 s
Aug 29, 20265.3 s
Sep 5, 20264.6 s
Sep 12, 20262.9 s
Sep 19, 20262.7 s
Sep 26, 20262.8 s
Oct 3, 20262.9 s
Oct 10, 20263.0 s
Oct 17, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
405 ms130 msMay 2Oct 17258 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026373 ms
May 9, 2026358 ms
May 16, 2026335 ms
May 23, 2026318 ms
May 30, 2026307 ms
Jun 6, 2026293 ms
Jun 13, 2026285 ms
Jun 20, 2026285 ms
Jun 27, 2026282 ms
Jul 4, 2026280 ms
Jul 11, 2026288 ms
Jul 18, 2026289 ms
Jul 25, 2026293 ms
Aug 1, 2026297 ms
Aug 8, 2026304 ms
Aug 22, 2026247 ms
Aug 29, 2026195 ms
Sep 5, 2026162 ms
Sep 12, 2026171 ms
Sep 19, 2026211 ms
Sep 26, 2026240 ms
Oct 3, 2026256 ms
Oct 10, 2026259 ms
Oct 17, 2026258 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 unitagstore.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. unitagstore.com at 1.9 s1.9 s
  2. unitagstore.com at 3.8 s3.8 s
  3. unitagstore.com at 5.7 s5.7 s
  4. unitagstore.com at 7.6 s7.6 s
  5. unitagstore.com at 9.5 s9.5 s
  6. unitagstore.com at 11.4 s11.4 s
  7. unitagstore.com at 13.3 s13.3 s
  8. unitagstore.com at 15.2 s15.2 s

Speed

8 to fix62
  • Improve image delivery

    150 ms · 976 KiB

    27 images could be 976 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused JavaScript

    750 ms · 361 KiB

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

  • Mobile performance score: 62

    62/100

    Your mobile performance score is 62 (desktop: 69). 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 (Google Tag Manager, Facebook and TikTok and others), adding 1.9 MB and 738 ms of main-thread time.

  • Google Tag Manager adds 290 ms

    290 ms

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

  • Facebook adds 276 ms

    276 ms

    Facebook costs a phone 276 ms of main-thread work and 272 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.

  • Main-thread work: 2.5 s

    A phone's processor spends 2.5 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • unitag.co.id adds 0 ms

    0 ms

    unitag.co.id costs a phone 0 ms of main-thread work and 1.3 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.

  • Use efficient cache lifetimes

    150 ms · 245 KiB

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

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 46 KiB

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

  • Render-blocking requests

    150 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 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.

1 checks passed
  • Server response: 218 ms

    218 ms

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

Core Web Vitals

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

  • Speed Index: 17.6 s

    17.6 s

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

  • Time to Interactive: 11.6 s

    11.6 s

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

  • Largest Contentful Paint: 4.4 s

    4.4 s

    Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “New Arrivals B01 & B02 Urban Gear Sling Bag”. Most of its time is resource load delay (8.5 s).

  • Real-user INP: 201 ms

    201 ms

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

  • Total Blocking Time: 457 ms

    457 ms

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

8 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user CLS: 0.08

    0.08

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 793 ms

    793 ms

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

  • Tap response (INP) got 29% faster for real visitors

    -29%

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

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

    -50%

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix69
  • Page weight: 2.6 MB in 123 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 123 requests on a phone: images 1.4 MB (39), scripts 1.0 MB (29) and other files 128 KiB (51). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    promo-rilis-iphone-18-series-a46fb01c.webp 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).

  • 6 images far larger than shown

    425 KiB

    6 images are downloaded at several times the size a phone draws them, for example promo-banner-rilis-iphone-18-series-e6d1c2b9.webp at 1,080 px wide, shown at 161 px. Resized copies would save about 425 KiB.

  • 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.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

4 to fixGoogle 9394
  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

  • 2 text elements with low contrast

    2 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 (1 element)

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • 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 54 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 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

1 to fixGoogle 10097
  • No social preview image

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

  • 64 internal links, 16 external

    The homepage links to 64 pages on unitagstore.com and 16 external pages.

7 checks passed
  • Meta description: 94 characters

    Your meta description is 94 characters: “Toko resmi UniTAG. Menyediakan berbagai aksesoris gadget premium dengan jaminan 100% Original.”.

  • One H1 headline

    Your main headline reads: “UniTAG Store - Trusted Accessories Gadget”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “UniTAG Store - Trusted Accessories Gadget”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

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

Other pages

3 to fix86
  • 2 linked pages hidden from search

    https://unitagstore.com/akun and https://unitagstore.com/koleksi/travel-adaptor are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 6 pages share a meta description

    https://unitagstore.com/produk, https://unitagstore.com/koleksi/b1g1, https://unitagstore.com/akun, https://unitagstore.com/koleksi/travel-adaptor, https://unitagstore.com/koleksi/powerbank and https://unitagstore.com/brands/spigen use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://unitagstore.com/akun and https://unitagstore.com/brands/spigen have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://unitagstore.com/brands/spigen has 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.

  • 1 page slow to respond

    https://unitagstore.com/brands/spigen took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 46 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 567 words of visible text.

4 checks passed
  • 1 call to action

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

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics, Meta Pixel, TikTok Pixel and Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 10 cookies set on arrival

    10

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

  • 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 unitagstore.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Analytics
Hosting
Vercel

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on unitagstore.com, including 14 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