Website review, no card needed

starstalentstudio.com logo

starstalentstudio.com website review

Visit site (opens in a new tab)Reviewed 25 October 202634 issues · 90 checks

This review found 34 issues worth fixing on starstalentstudio.com, 13 of them high impact, across 90 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
7.0 s4.0 sMay 2Oct 174.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20266.6 s
May 9, 20266.2 s
May 16, 20266.0 s
May 23, 20266.2 s
May 30, 20266.3 s
Jun 6, 20266.6 s
Jun 13, 20266.4 s
Jun 20, 20266.1 s
Jun 27, 20266.3 s
Jul 4, 20266.1 s
Jul 11, 20266.0 s
Jul 18, 20265.7 s
Jul 25, 20265.4 s
Aug 1, 20265.6 s
Aug 8, 20265.5 s
Aug 15, 20265.8 s
Aug 22, 20266.0 s
Aug 29, 20266.2 s
Sep 5, 20266.4 s
Sep 12, 20266.5 s
Sep 19, 20266.5 s
Sep 26, 20266.6 s
Oct 3, 20266.5 s
Oct 10, 20266.0 s
Oct 17, 20264.3 s
Real-visitor tap response (INP)75th percentile, phones
254 ms147 msMay 2Oct 17196 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026227 ms
May 9, 2026179 ms
May 16, 2026186 ms
May 23, 2026170 ms
May 30, 2026177 ms
Jun 6, 2026172 ms
Jun 13, 2026177 ms
Jun 20, 2026194 ms
Jun 27, 2026196 ms
Jul 4, 2026241 ms
Jul 11, 2026228 ms
Jul 18, 2026212 ms
Jul 25, 2026194 ms
Aug 1, 2026173 ms
Aug 8, 2026173 ms
Aug 15, 2026159 ms
Aug 22, 2026173 ms
Aug 29, 2026191 ms
Sep 5, 2026223 ms
Sep 12, 2026242 ms
Sep 19, 2026200 ms
Sep 26, 2026213 ms
Oct 3, 2026191 ms
Oct 10, 2026184 ms
Oct 17, 2026196 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 starstalentstudio.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix55
  • Use efficient cache lifetimes

    1.6 s · 407 KiB

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

  • Render-blocking requests

    1.6 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and syngency.com and others), adding 1.8 MB and 1.8 s of main-thread time.

  • Reduce unused JavaScript

    920 ms · 752 KiB

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

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55 (desktop: 98). Pages that score under 90 lose visitors before the first paint.

  • Google CDN adds 878 ms

    878 ms

    Google CDN costs a phone 878 ms of main-thread work and 734 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 Tag Manager adds 496 ms

    496 ms

    Google Tag Manager costs a phone 496 ms of main-thread work and 377 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: 4.0 s

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

  • 20 long tasks on the main thread

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

  • syngency.com adds 250 ms

    250 ms

    syngency.com costs a phone 250 ms of main-thread work and 396 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.

  • Improve image delivery

    150 ms · 39 KiB

    1 image could be 39 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 CSS

    178 KiB

    About 178 KiB of CSS is downloaded but never applied on this page.

  • Font display

    50 ms

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

  • Phones get a much slower page than desktops

    Desktop scores 98 but mobile only 55. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Legacy JavaScript

    10 KiB

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

  • 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

    3 KiB

    3 KiB could be saved by minifying JavaScript.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

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

  • Real-user FCP: 3.2 s

    3.2 s

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

  • Real-user TTFB: 2.6 s

    2.6 s

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

  • Time to Interactive: 13.2 s

    13.2 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Largest Contentful Paint: 4.6 s

    4.6 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -6%

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

5 checks passed
  • Real-user INP: 166 ms

    166 ms

    Real visitors wait 166 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.

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

    -19%

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

  • Speed Index: 3.0 s

    3.0 s

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

1 to fix85
  • Page weight: 2.1 MB in 43 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 43 requests on a phone: scripts 1.3 MB (15), other files 445 KiB (8) and fonts 123 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (117 KiB) 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.6 g of CO₂ per visit

    0.60 g

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

2 checks passed
  • Images load when needed

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8492
  • Certain ARIA roles must be contained by particular parents (8 elements)

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

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 form fields without a label

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

  • Headings skip levels

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

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

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 4 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

2 to fixGoogle 10091
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (208 characters)

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

  • 70 internal links, 6 external

    The homepage links to 70 pages on starstalentstudio.com and 6 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Utah Modeling & Talent Agency”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Utah Modeling & Talent Agency | Stars Talent Studio”.

  • Canonical URL set

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

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

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://starstalentstudio.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 (255 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 12 pages share 4 titles

    https://starstalentstudio.com/divisions/modeling, https://starstalentstudio.com/divisions/modeling/men and https://starstalentstudio.com/divisions/modeling/women all use the title “Utah Modeling Agency | Stars Talent Studio”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages share a meta description

    https://starstalentstudio.com/divisions/modeling, https://starstalentstudio.com/divisions/modeling/men and https://starstalentstudio.com/divisions/modeling/women use the same meta description. A description written for each page earns more clicks.

  • 12 pages slow to respond

    https://starstalentstudio.com/divisions/modeling, https://starstalentstudio.com/divisions/modeling/men, https://starstalentstudio.com/divisions/modeling/women, https://starstalentstudio.com/divisions/acting, https://starstalentstudio.com/divisions/acting/men and https://starstalentstudio.com/divisions/acting/women and 6 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    65 of 69 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

    The homepage carries about 253 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact”, “Apply for representation” and “Contact Us”.

  • 1 short form

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

  • Analytics in place

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

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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 starstalentstudio.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
Tailwind CSS
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on starstalentstudio.com, including 19 speed issues, 2 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