Website review, no card needed

upstock.io logo

upstock.io website review

Visit site (opens in a new tab)Reviewed 22 October 202640 issues · 85 checks

This review found 40 issues worth fixing on upstock.io, 15 of them high impact, across 85 checks. The most urgent: improve image delivery. 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 upstock.io (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. upstock.io at 1.0 s1.0 s
  2. upstock.io at 2.1 s2.1 s
  3. upstock.io at 3.1 s3.1 s
  4. upstock.io at 4.2 s4.2 s
  5. upstock.io at 5.2 s5.2 s
  6. upstock.io at 6.2 s6.2 s
  7. upstock.io at 7.3 s7.3 s
  8. upstock.io at 8.3 s8.3 s

Speed

14 to fix38
  • Improve image delivery

    6.5 s · 1.4 MB

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

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 38

    38/100

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

  • Main-thread work: 4.3 s

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

  • Use efficient cache lifetimes

    900 ms · 537 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klevu Search, Google Maps and ShareThis and others), adding 1.4 MB and 1.2 s of main-thread time.

  • Reduce unused JavaScript

    610 ms · 436 KiB

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

  • Reduce unused CSS

    760 ms · 117 KiB

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

  • 9 long tasks on the main thread

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

  • Legacy JavaScript

    300 ms · 48 KiB

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

  • Google Maps adds 280 ms

    280 ms

    Google Maps costs a phone 280 ms of main-thread work and 395 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.

  • Klevu Search adds 294 ms

    294 ms

    Klevu Search costs a phone 294 ms of main-thread work and 149 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.

  • mothercare.co.id adds 208 ms

    208 ms

    mothercare.co.id costs a phone 208 ms of main-thread work and 572 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.

  • 1,956 HTML elements

    The page has 1,956 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Minify JavaScript

    29 KiB

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

1 checks passed
  • Server response: 435 ms

    435 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • Largest Contentful Paint: 15.5 s

    15.5 s

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

  • Time to Interactive: 17.3 s

    17.3 s

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

  • First Contentful Paint: 4.2 s

    4.2 s

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

  • Total Blocking Time: 963 ms

    963 ms

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

  • Speed Index: 6.8 s

    6.8 s

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • 7 images without width and height

    7 images have no width and height attributes, so the layout jumps as each one loads.

5 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 197 ms

    197 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user TTFB: 647 ms

    647 ms

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

  • Cumulative Layout Shift: 0.068

    0.068

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

Images and page weight

3 to fix60
  • 1 image over 500 KB

    logo-final.gif weighs 1.3 MB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.5 MB in 220 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 220 requests on a phone: images 1.7 MB (32), scripts 1.1 MB (131) and other files 507 KiB (43). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    378 KiB

    1 image is downloaded at several times the size a phone draws it, for example logo-final.gif at 546 px wide, shown at 155 px. Resized copies would save about 378 KiB.

  • 1 image in older formats

    1 image (180 KiB) is 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.

  • About 1.0 g of CO₂ per visit

    1.00 g

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

1 checks passed
  • Images load when needed

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

Accessibility

3 to fixGoogle 8896
  • 4 images without alt text

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

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

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

  • 2 links without text

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

  • Headings skip levels

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

1 checks passed
  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 4 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 9289
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “EGP88 -> Nikmati Hari Dengan Bocoran Rtp Game Hari Ini Gacor Gokil”.

  • No XML sitemap

    No XML sitemap at https://bocoranrtphariini.com/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 461 internal links, 3 external

    The homepage links to 461 pages on upstock.io and 3 external pages.

6 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “Nikmati harimu dengan bocoran RTP game hari ini yang gacor gokil di EGP88! Dapatkan referensi pola akurat untuk maksima…”.

  • One H1 headline

    Your main headline reads: “EGP88 -> Nikmati Hari Dengan Bocoran Rtp Game Hari Ini Gacor Gokil”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, FAQPage and Organization.

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

AI search readiness

100
  • No llms.txt

    There is no https://bocoranrtphariini.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.

3 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: 6 of 6 facts

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

  • Text is in the HTML

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

Other pages

4 to fix53
  • 14 linked pages are broken

    Your homepage links to https://bocoranrtphariini.com/brand-a-z/addo.html, https://bocoranrtphariini.com/brand-a-z/adidas.html, https://bocoranrtphariini.com/brand-a-z/airfree.html, https://bocoranrtphariini.com/brand-a-z/alamii.html, https://bocoranrtphariini.com/brand-a-z/amara.html and https://bocoranrtphariini.com/brand-a-z/aqua-scale.html and 8 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 page points its canonical at the homepage

    https://bocoranrtphariini.com/nikmati declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://bocoranrtphariini.com/nikmati all use the title “EGP88 -> Nikmati Hari Dengan Bocoran Rtp Game Hari Ini Gacor Gokil”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without an H1

    https://bocoranrtphariini.com/nikmati has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://bocoranrtphariini.com/nikmati 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.

  • 15 internal pages checked

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

3 checks passed
  • Every page has a meta description

    All 1 page that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 1 page that loaded have a <title>.

Best practices

4 to fixGoogle 4686
  • 3 third-party cookies

    3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://www.mothercare.co.id/static/version1741963345/frontend/Codilar/mothercare/id_ID/fonts/mother…”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 524 words of copy

    The homepage carries about 524 words of visible text.

5 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “download apps”, “Contact Us” and “contact us”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 14 testimonial or review blocks, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics 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
  • 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.

  • 27 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
Magento
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on upstock.io, including 22 speed issues, 2 SEO issues and 1 conversion gap. 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