Website review, no card needed

shopaubreyjaymes.com logo

shopaubreyjaymes.com website review

Visit site (opens in a new tab)Reviewed 20 November 202662 issues · 101 checks

This review found 62 issues worth fixing on shopaubreyjaymes.com, 32 of them high impact, across 101 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

Real-visitor load time (LCP)75th percentile, phones
3.0 s2.2 sOct 24Nov 142.3 s
Show as table
DateReal-visitor load time (LCP)
Oct 24, 20262.9 s
Oct 31, 20262.5 s
Nov 7, 20262.4 s
Nov 14, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
194 ms185 msOct 24Nov 14186 ms
Show as table
DateReal-visitor tap response (INP)
Oct 24, 2026191 ms
Oct 31, 2026193 ms
Nov 7, 2026187 ms
Nov 14, 2026186 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 shopaubreyjaymes.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. shopaubreyjaymes.com at 1.2 s1.2 s
  2. shopaubreyjaymes.com at 2.5 s2.5 s
  3. shopaubreyjaymes.com at 3.7 s3.7 s
  4. shopaubreyjaymes.com at 5.0 s5.0 s
  5. shopaubreyjaymes.com at 6.2 s6.2 s
  6. shopaubreyjaymes.com at 7.4 s7.4 s
  7. shopaubreyjaymes.com at 8.7 s8.7 s
  8. shopaubreyjaymes.com at 9.9 s9.9 s

Speed

13 to fix35
  • Use efficient cache lifetimes

    14.7 s · 3.7 MB

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

  • Improve image delivery

    12.9 s · 3.8 MB

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

  • Reduce unused JavaScript

    1.6 s · 716 KiB

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

  • Render-blocking requests

    1.5 s

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

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 8.2 s

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

  • 4,042 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Adobe Tag Manager, Facebook and sprinklr.com and others), adding 1.6 MB and 1.8 s of main-thread time.

  • Adobe Tag Manager adds 416 ms

    416 ms

    Adobe Tag Manager costs a phone 416 ms of main-thread work and 148 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 375 ms

    375 ms

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

  • 20 long tasks on the main thread

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

  • sprinklr.com adds 293 ms

    293 ms

    sprinklr.com costs a phone 293 ms of main-thread work and 439 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 Maps adds 147 ms

    147 ms

    Google Maps costs a phone 147 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.

  • Legacy JavaScript

    150 ms · 39 KiB

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

  • Minify JavaScript

    7 KiB

    7 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: 27 ms

    27 ms

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

Core Web Vitals

12 to fix33
  • 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 INP: 526 ms

    526 ms

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

  • Largest Contentful Paint: 21.0 s

    21.0 s

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

  • Time to Interactive: 24.2 s

    24.2 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • Speed Index: 6.3 s

    6.3 s

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

  • Real-user LCP: 3.6 s

    3.6 s

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 863 ms

    863 ms

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

  • 38 images without width and height

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

  • Cumulative Layout Shift: 0.18

    0.18

    The layout shifts by 0.18 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Tap response (INP) held steady for real visitors

    -3%

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

2 checks passed
  • Real-user CLS: 0.00

    0.00

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

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

    -15%

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

Images and page weight

4 to fix25
  • Page weight: 6.0 MB in 156 requests

    6.0 MB

    Your homepage downloads 6.0 MB in 156 requests on a phone: images 3.9 MB (14), scripts 1.9 MB (78) and HTML 92 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 3.8 MB together. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    1.7 MB

    2 images are downloaded at several times the size a phone draws them, for example asw.png at 1,254 px wide, shown at 351 px. Resized copies would save about 1.7 MB.

  • 1 image in older formats

    1 image (2.7 MB) 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.7 g of CO₂ per visit

    1.71 g

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

17 to fixGoogle 5880
  • 147 tap targets too small

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

  • Certain ARIA roles must be contained by particular parents (18 elements)

    Certain ARIA roles must be contained by particular parents: 18 elements on the page fail this check, rated critical by axe-core.

  • 6 buttons without a name

    6 buttons have no accessible name, so screen readers announce just “button”.

  • Certain ARIA roles must contain particular children (3 elements)

    Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.

  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • ARIA dialog and alertdialog nodes should have an accessible name (32 elements)

    ARIA dialog and alertdialog nodes should have an accessible name: 32 elements on the page fail this check, rated serious by axe-core.

  • Orphan list items

    Some list items are not inside a list.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 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 (126 elements)

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

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Elements use prohibited ARIA attributes

    Elements use prohibited ARIA attributes (1 element).

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (35 elements).

1 checks passed
  • 54 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 69 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 15 failed. 7 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
  • 2 H1 headlines

    There are 2 <h1> headlines (“RAKSASAWIN | Link Slot Gacor Gampang Menang & Hok…” and “RAKSASAWIN | Link Slot Gacor Gampang Menang & Hok…”). One clear main headline is easier for people and search engines.

  • 25 links crawlers can't follow

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

  • Meta description is long (175 characters)

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

  • 76 internal links, 4 external

    The homepage links to 76 pages on shopaubreyjaymes.com and 4 external pages.

6 checks passed
  • Title: 61 characters

    Your title is a healthy 61 characters: “RAKSASAWIN | Link Slot Gacor Gampang Menang & Hoki Lagi Viral”.

  • Canonical URL set

    The canonical URL is https://www.sarasotaconcertband.org/.

  • Structured data in place

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

  • 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://www.sarasotaconcertband.org/sitemap.xml.

AI search readiness

1 to fix88
  • 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://www.sarasotaconcertband.org/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 (3,369 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix58
  • 3 linked pages are broken

    Your homepage links to https://www.sarasotaconcertband.org/kebijakan-privasi, https://www.sarasotaconcertband.org/legal and https://www.sarasotaconcertband.org/sitemap, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 page points its canonical at the homepage

    https://www.sarasotaconcertband.org/board-recruitment 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://www.sarasotaconcertband.org/board-recruitment all use the title “RAKSASAWIN | Link Slot Gacor Gampang Menang & Hoki Lagi Viral”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page with very little text

    https://www.sarasotaconcertband.org/board-recruitment 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.

  • 4 internal pages checked

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

4 checks passed
  • Every page has a meta description

    All 1 page 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 1 page that loaded have a <title>.

Best practices

6 to fixGoogle 5068
  • 5 broken images

    5 images failed to load on a phone, for example https://www.sarasotaconcertband.org/#.

  • 46 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 third-party cookie

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Unsafe attempt to load URL https://www.samsung.com/etc.clientlibs/samsung/clientlibs/consumer/global/clientlib-common/r…”.

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

  • About 1,800 words of copy

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

5 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “RAKSASAWIN Explore Shop” and “Shop”.

  • 9 short forms

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

  • Social proof on the page

    Social proof on the homepage: 70 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

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 Pinterest Tag (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.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 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 shopaubreyjaymes.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 62 issues on shopaubreyjaymes.com, including 25 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