Website review, no card needed

advancedgraphicswear.com logo

advancedgraphicswear.com website review

Visit site (opens in a new tab)Reviewed 7 November 202641 issues · 85 checks

This review found 41 issues worth fixing on advancedgraphicswear.com, 21 of them high impact, across 85 checks. The most urgent: use efficient cache lifetimes. 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 advancedgraphicswear.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. advancedgraphicswear.com at 1.9 s1.9 s
  2. advancedgraphicswear.com at 3.7 s3.7 s
  3. advancedgraphicswear.com at 5.6 s5.6 s
  4. advancedgraphicswear.com at 7.4 s7.4 s
  5. advancedgraphicswear.com at 9.3 s9.3 s
  6. advancedgraphicswear.com at 11.2 s11.2 s
  7. advancedgraphicswear.com at 13.0 s13.0 s
  8. advancedgraphicswear.com at 14.9 s14.9 s

Speed

13 to fix32
  • Use efficient cache lifetimes

    17.3 s · 4.8 MB

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

  • Improve image delivery

    13.8 s · 4.5 MB

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

  • istudiosg.com adds 2.5 s

    2.5 s

    istudiosg.com costs a phone 2.5 s of main-thread work and 1.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    2.0 s

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

  • Main-thread work: 15.4 s

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

  • Mobile performance score: 32

    32/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (istudiosg.com, Yellow Robot and Cloudflare and others), adding 2.3 MB and 3.0 s of main-thread time.

  • Reduce unused JavaScript

    900 ms · 290 KiB

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

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    300 ms · 41 KiB

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

  • Yellow Robot adds 289 ms

    289 ms

    Yellow Robot costs a phone 289 ms of main-thread work and 44 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.

  • 2,463 HTML elements

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

  • imgmio.io adds 0 ms

    0 ms

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    21 KiB

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

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

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

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 9 ms

    9 ms

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

Core Web Vitals

6 to fix33
  • Largest Contentful Paint: 31.5 s

    31.5 s

    Your largest element takes 31.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “MIOTOTO | Explore Bet 100 Perak di Toto Macau Terpercaya”.

  • Total Blocking Time: 4.9 s

    4.9 s

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

  • Time to Interactive: 31.8 s

    31.8 s

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

  • Speed Index: 10.1 s

    10.1 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • 5 images without width and height

    5 images 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.036

    0.036

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

Images and page weight

4 to fix25
  • Page weight: 8.5 MB in 136 requests

    8.5 MB

    Your homepage downloads 8.5 MB in 136 requests on a phone: images 6.4 MB (23), scripts 671 KiB (40) and fonts 569 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 4.4 MB together. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    2.6 MB

    3 images are downloaded at several times the size a phone draws them, for example bet100-totomacau.jpg at 2,037 px wide, shown at 84 px. Resized copies would save about 2.6 MB.

  • 6 images in older formats

    6 images (4.9 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 2.4 g of CO₂ per visit

    2.42 g

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

6 to fixGoogle 8090
  • 13 text elements with low contrast

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

  • Elements must only use permitted ARIA attributes (3 elements)

    Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 3 images without alt text

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

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

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

  • Headings skip levels

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

1 checks passed
  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 7 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 8588
  • 10 H1 headlines

    There are 10 <h1> headlines (“MIOTOTO | Explore Bet 100 Perak di Toto Macau Ter…”, “MIOTOTO | Explore Bet 100 Perak di Toto Macau Ter…” and “Limited Time Promotion”). One clear main headline is easier for people and search engines.

  • Meta description is long (170 characters)

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

  • 4 links crawlers can't follow

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

  • 22 internal links, 82 external

    The homepage links to 22 pages on advancedgraphicswear.com and 82 external pages.

6 checks passed
  • Title: 56 characters

    Your title is a healthy 56 characters: “MIOTOTO | Explore Bet 100 Perak di Toto Macau Terpercaya”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, FAQPage, Organization, Product and SoftwareApplication.

  • 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://bettotomacau.com/sitemap.xml.

AI search readiness

2 to fix73
  • Snippets are switched off

    The robots meta tag says “index, follow, nosnippet”, which tells Google, Bing and the AI answers built on them not to quote this page.

  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing 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://bettotomacau.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,910 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix81
  • 2 pages point its canonical at the homepage

    https://bettotomacau.com/pages/applecare-landing-page and https://bettotomacau.com/products/iphone-17-pro-mg8h4x-a declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 3 pages share a title

    /, https://bettotomacau.com/pages/applecare-landing-page and https://bettotomacau.com/products/iphone-17-pro-mg8h4x-a all use the title “MIOTOTO | Explore Bet 100 Perak di Toto Macau Terpercaya”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://bettotomacau.com/pages/applecare-landing-page and https://bettotomacau.com/products/iphone-17-pro-mg8h4x-a use the same meta description. A description written for each page earns more clicks.

  • 2 pages slow to respond

    https://bettotomacau.com/pages/applecare-landing-page and https://bettotomacau.com/products/iphone-17-pro-mg8h4x-a took over 3 s to send their HTML from our server.

  • 2 internal pages checked

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

5 checks passed
  • Linked pages load

    All 2 pages we checked loaded without an error.

  • Every page has a meta description

    All 2 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 2 pages that loaded have a <title>.

Best practices

2 to fixGoogle 6987
  • 9 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://bettotomacau.com/' was loaded over HTTPS, but requested an insecure stylesheet 'htt…”.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

  • Browser-reported issues

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

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 1,058 words of copy

    The homepage carries about 1,058 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Buy It Now”, “Contact Us” and “Why Shop at iStudio”.

  • 6 short forms

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

  • Social proof on the page

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

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 11 other companies contacted

    Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 advancedgraphicswear.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 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

backinstock.org

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

E-commerce
Shopify
Hosting
Cloudflare

Company

Headquarters
Whitney Point

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on advancedgraphicswear.com, including 19 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