Website review, no card needed

futuresupplychains.com logo

futuresupplychains.com website review

Visit site (opens in a new tab)Reviewed 29 October 202645 issues · 82 checks

This review found 45 issues worth fixing on futuresupplychains.com, 17 of them high impact, across 82 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

Real-visitor load time (LCP)75th percentile, phones
3.4 s3.4 sOct 3Oct 243.4 s
Show as table
DateReal-visitor load time (LCP)
Oct 3, 20263.4 s
Oct 10, 20263.4 s
Oct 17, 20263.4 s
Oct 24, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
225 ms223 msOct 3Oct 24225 ms
Show as table
DateReal-visitor tap response (INP)
Oct 3, 2026223 ms
Oct 10, 2026224 ms
Oct 17, 2026224 ms
Oct 24, 2026225 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 futuresupplychains.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix72
  • Improve image delivery

    11.3 s · 2.2 MB

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

  • Use efficient cache lifetimes

    9.3 s · 1.8 MB

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

  • Mobile performance score: 72

    72/100

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

  • Reduce unused JavaScript

    470 ms · 218 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Other Google APIs/SDKs, teepublic.com and Google Tag Manager and others), adding 3.0 MB and 237 ms of main-thread time.

  • Render-blocking requests

    450 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 450 ms.

  • mariterbang.io adds 0 ms

    0 ms

    mariterbang.io costs a phone 0 ms of main-thread work and 2.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.

  • teepublic.com adds 57 ms

    57 ms

    teepublic.com costs a phone 57 ms of main-thread work and 397 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

    160 ms · 40 KiB

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

  • Legacy JavaScript

    150 ms · 21 KiB

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

  • 2 long tasks on the main thread

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

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

2 checks passed
  • Main-thread work: 0.8 s

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

  • Server response: 10 ms

    10 ms

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

Core Web Vitals

9 to fix0
  • 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.

  • Real-user CLS: 0.61

    0.61

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

  • Largest Contentful Paint: 16.1 s

    16.1 s

    Your largest element takes 16.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “MAWARTOTO » Link Situs Slot Gacor Hari Ini Dengan Peluang M…”.

  • Time to Interactive: 16.1 s

    16.1 s

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

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Real-user INP: 235 ms

    235 ms

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    0%

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

4 checks passed
  • Real-user TTFB: 664 ms

    664 ms

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

  • Speed Index: 2.6 s

    2.6 s

    Visually, the page fills in at 2.6 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 10 ms

    10 ms

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

Images and page weight

4 to fix40
  • 1 image over 500 KB

    MYh2sVqx.png weighs 2.0 MB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    606 KiB

    1 image is downloaded at several times the size a phone draws it, for example MYh2sVqx.png at 1,254 px wide, shown at 350 px. Resized copies would save about 606 KiB.

  • Page weight: 3.1 MB in 43 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 43 requests on a phone: images 2.3 MB (20), scripts 501 KiB (14) and fonts 142 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (2.0 MB) are 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 0.9 g of CO₂ per visit

    0.88 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.88 g of CO₂e: 105.7 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

11 to fixGoogle 6885
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 6 text elements with low contrast

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

  • 33 images without alt text

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

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

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

  • No main landmark

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 1 form field without a label

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

3 to fixGoogle 7781
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is long (90 characters)

    Your title is 90 characters, so Google will cut it off around 60: “MAWARTOTO » Link Situs Slot Gacor Hari Ini Dengan Peluang Menang Besar Hanya di MAWAR TOTO”.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

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

  • 130 internal links, 11 external

    The homepage links to 130 pages on futuresupplychains.com and 11 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “MAWARTOTO » Link Situs Slot Gacor Hari Ini Dengan Peluang Menang Besar Hanya di MAWAR TOTO”.

  • Canonical URL set

    The canonical URL is https://linksitusslotgacorhariini.com/slotgacor/.

  • Structured data in place

    Structured data found: BreadcrumbList, FAQPage, ImageObject, Organization and WebPage.

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

  • XML sitemap found

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

Other pages

1 to fix0
  • 15 linked pages are broken

    Your homepage links to https://linksitusslotgacorhariini.com/order/status, https://linksitusslotgacorhariini.com/contact, https://linksitusslotgacorhariini.com/shipping, https://linksitusslotgacorhariini.com/sizechart, https://linksitusslotgacorhariini.com/about and https://linksitusslotgacorhariini.com/intellectual-property-policy and 9 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 15 internal pages checked

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

Best practices

5 to fixGoogle 6969
  • 7 broken images

    7 images failed to load on a phone, for example https://assets.teepublic.com/assets/teepublicons/x_close_orange400-c1926221e50e7f6686d23ac344405449054e43f23d0f3306f15d8dfd546f999a.svg.

  • 5 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Unexpected identifier 'n'”.

  • 1 distorted image

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

  • Browser-reported issues

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

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 840 words of copy

    The homepage carries about 840 words of visible text.

4 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Order Status”, “Contact Us” and “Artist Signup”.

  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 35 testimonial or review blocks, 1 customer or partner logo, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

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

  • 6 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on futuresupplychains.com, including 17 speed issues, 3 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