Website review, no card needed

bicoastalmgmt.com logo

bicoastalmgmt.com website review

Visit site (opens in a new tab)Reviewed 31 October 202626 issues · 74 checks

This review found 26 issues worth fixing on bicoastalmgmt.com, 4 of them high impact, across 74 checks. The most urgent: fails Core Web Vitals for real visitors. 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
2.7 s1.3 sMay 9Oct 242.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.3 s
May 16, 20262.3 s
May 23, 20262.5 s
May 30, 20261.5 s
Jun 6, 20261.4 s
Jun 13, 20261.7 s
Jun 20, 20261.6 s
Jun 27, 20262.2 s
Jul 4, 20262.3 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.1 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.7 s
Aug 22, 20261.9 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20262.2 s
Sep 19, 20261.7 s
Sep 26, 20261.9 s
Oct 3, 20262.0 s
Oct 10, 20261.8 s
Oct 17, 20262.2 s
Oct 24, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
273 ms109 msMay 23Oct 24156 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026254 ms
May 30, 2026146 ms
Jun 6, 2026145 ms
Jun 13, 2026146 ms
Jun 20, 2026141 ms
Jun 27, 2026164 ms
Jul 4, 2026183 ms
Jul 11, 2026162 ms
Jul 18, 2026162 ms
Jul 25, 2026146 ms
Aug 1, 2026136 ms
Aug 8, 2026140 ms
Aug 15, 2026136 ms
Aug 22, 2026143 ms
Aug 29, 2026141 ms
Sep 5, 2026129 ms
Sep 12, 2026135 ms
Sep 19, 2026135 ms
Sep 26, 2026128 ms
Oct 3, 2026144 ms
Oct 10, 2026174 ms
Oct 17, 2026159 ms
Oct 24, 2026156 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 bicoastalmgmt.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bicoastalmgmt.com at 1.2 s1.2 s
  2. bicoastalmgmt.com at 2.5 s2.5 s
  3. bicoastalmgmt.com at 3.7 s3.7 s
  4. bicoastalmgmt.com at 4.9 s4.9 s
  5. bicoastalmgmt.com at 6.1 s6.1 s
  6. bicoastalmgmt.com at 7.4 s7.4 s
  7. bicoastalmgmt.com at 8.6 s8.6 s
  8. bicoastalmgmt.com at 9.8 s9.8 s

Speed

6 to fix71
  • Mobile performance score: 71

    71/100

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

  • Use efficient cache lifetimes

    697 KiB

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

  • Reduce unused JavaScript

    450 ms · 164 KiB

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

  • Improve image delivery

    270 KiB

    2 images could be 270 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Main-thread work: 2.1 s

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

  • portfoliopad.com adds 0 ms

    0 ms

    portfoliopad.com costs a phone 0 ms of main-thread work and 697 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 · 12 KiB

    Polyfills for old browsers add 12 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 153 ms. During a long task the page ignores taps.

  • Render-blocking requests

    150 ms

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (portfoliopad.com), adding 697 KiB and 0 ms of main-thread time.

  • 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: 62 ms

    62 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 5.6 s

    5.6 s

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

  • Speed Index: 8.4 s

    8.4 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • Time to Interactive: 5.7 s

    5.7 s

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

6 checks passed
  • Real-user INP: 156 ms

    156 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • Tap response (INP) got 21% faster for real visitors

    -21%

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 89 ms

    89 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix90
  • 2 images far larger than shown

    118 KiB

    2 images are downloaded at several times the size a phone draws them, for example 004.jpg at 1,425 px wide, shown at 358 px. Resized copies would save about 118 KiB.

  • 3 images in older formats

    3 images (365 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.4 g of CO₂ per visit

    0.35 g

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

2 checks passed
  • Page weight: 1.2 MB in 50 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 50 requests on a phone: images 701 KiB (7), scripts 403 KiB (28) and other files 75 KiB (10). That is a lean page.

  • Images load when needed

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

Accessibility

1 to fixGoogle 9699
  • 19 links without text

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

2 checks passed
  • Every image has alt text

    All 32 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

SEO

2 to fixGoogle 9291
  • 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 (164 characters)

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

  • No X (Twitter) card tag

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

  • 34 internal links, 1 external

    The homepage links to 34 pages on bicoastalmgmt.com and 1 external page.

6 checks passed
  • One H1 headline

    Your main headline reads: “Home”.

  • Title: 64 characters

    Your title is a healthy 64 characters: “BICOASTAL MGMT Fashion Commercial Kids Plus and Fit model agency”.

  • Canonical URL set

    The canonical URL is https://www.bicoastalmgmt.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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.bicoastalmgmt.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://www.bicoastalmgmt.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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 (169 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 8 pages without a meta description

    https://www.bicoastalmgmt.com/news/8350/silvia-for-judy-blue-denim, https://www.bicoastalmgmt.com/news/8351/zane-and-stephen-for-riverline, https://www.bicoastalmgmt.com/news/8352/payton-for-tinder, https://www.bicoastalmgmt.com/news/8250/karibel--jasmine-for-loreal, https://www.bicoastalmgmt.com/news/8200/the-peers-family-for-ello and https://www.bicoastalmgmt.com/news/8111/ruby-and-zane-for-spindrift and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.bicoastalmgmt.com/get-scouted, whose canonical is https://www.bicoastalmgmt.com/join. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 11 pages with very little text

    https://www.bicoastalmgmt.com/contact, https://www.bicoastalmgmt.com/news/8350/silvia-for-judy-blue-denim, https://www.bicoastalmgmt.com/news/8351/zane-and-stephen-for-riverline, https://www.bicoastalmgmt.com/news/8352/payton-for-tinder, https://www.bicoastalmgmt.com/news/8250/karibel--jasmine-for-loreal and https://www.bicoastalmgmt.com/news/8200/the-peers-family-for-ello and 5 others have 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 33 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    13 pages of 15 loaded without an error (the rest turned automated requests away).

  • Titles are unique

    Every page we checked has its own title.

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    9 of 10 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • Only about 196 words

    The homepage has only about 196 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

1 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Join Us” and “Contact Us”.

Privacy and tracking

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

  • 1 other company contacted

    Loading the homepage contacts 1 host 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 bicoastalmgmt.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
Next.js
Hosting
Netlify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on bicoastalmgmt.com, including 13 speed issues, 2 SEO issues and 5 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