Website review, no card needed

dressforsuccess.org logo

dressforsuccess.org website review

Visit site (opens in a new tab)Reviewed 30 October 202647 issues · 83 checks

This review found 47 issues worth fixing on dressforsuccess.org, 25 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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
1.7 s1.2 sMay 9Oct 241.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.5 s
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.5 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.3 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.5 s
Sep 19, 20261.6 s
Sep 26, 20261.7 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.5 s
Oct 24, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
143 ms99 msMay 9Oct 24116 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026116 ms
May 16, 2026120 ms
May 23, 2026128 ms
May 30, 2026129 ms
Jun 6, 2026138 ms
Jun 13, 2026136 ms
Jun 20, 2026122 ms
Jun 27, 2026122 ms
Jul 4, 2026113 ms
Jul 11, 2026113 ms
Jul 18, 2026104 ms
Jul 25, 2026107 ms
Aug 1, 2026110 ms
Aug 8, 2026111 ms
Aug 15, 2026118 ms
Aug 22, 2026112 ms
Aug 29, 2026113 ms
Sep 5, 2026113 ms
Sep 12, 2026121 ms
Sep 19, 2026135 ms
Sep 26, 2026136 ms
Oct 3, 2026128 ms
Oct 10, 2026127 ms
Oct 17, 2026113 ms
Oct 24, 2026116 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 dressforsuccess.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

13 to fix30
  • Reduce unused JavaScript

    15.1 s · 1.6 MB

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

  • Improve image delivery

    6.2 s · 2.3 MB

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

  • Use efficient cache lifetimes

    1.5 s · 2.0 MB

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

  • blackbaudcdn.net adds 1.8 s

    1.8 s

    blackbaudcdn.net costs a phone 1.8 s of main-thread work and 2.9 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

    1.1 s

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

  • Mobile performance score: 30

    30/100

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

  • Main-thread work: 5.5 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (blackbaudcdn.net, Google CDN and blackbaud.com and others), adding 4.5 MB and 3.0 s of main-thread time.

  • Reduce unused CSS

    910 ms · 117 KiB

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

  • 20 long tasks on the main thread

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

  • Minify JavaScript

    600 ms · 52 KiB

    52 KiB could be saved by minifying JavaScript.

  • Google CDN adds 378 ms

    378 ms

    Google CDN costs a phone 378 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 164 ms

    164 ms

    Google Tag Manager costs a phone 164 ms of main-thread work and 295 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 · 13 KiB

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

  • Minify CSS

    150 ms · 13 KiB

    13 KiB could be saved by minifying CSS.

  • Font display

    50 ms

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

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

    3 ms

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

Core Web Vitals

6 to fix100
  • First Contentful Paint: 21.0 s

    21.0 s

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

  • Largest Contentful Paint: 35.4 s

    35.4 s

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

  • Speed Index: 21.0 s

    21.0 s

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

  • Time to Interactive: 43.2 s

    43.2 s

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

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • 8 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -3%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.5 s

    1.5 s

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

  • Real-user INP: 116 ms

    116 ms

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 529 ms

    529 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 11.5 MB in 187 requests

    11.5 MB

    Your homepage downloads 11.5 MB in 187 requests on a phone: images 6.0 MB (44), scripts 4.0 MB (68) and other files 1.1 MB (43). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

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

  • 6 images far larger than shown

    1.2 MB

    6 images are downloaded at several times the size a phone draws them, for example Untitled-design-e1725552543605.png at 1,135 px wide, shown at 172 px. Resized copies would save about 1.2 MB.

  • 18 images in older formats

    18 images (2.6 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.

  • 7 images below the first screen load straight away

    7 images further down the page (1.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.3 g of CO₂ per visit

    3.27 g

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

Accessibility

8 to fixGoogle 7989
  • 1 button without a name

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

  • 5 tap targets too small

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

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

  • 2 images without alt text

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 6 links without text

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

  • 2 form fields without a label

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

1 checks passed
  • 46 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: 46 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 7760
  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (29 characters)

    Your title is only 29 characters: “Worldwide | Dress for Success”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 14 links with vague text

    14 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 48 internal links, 289 external

    The homepage links to 48 pages on dressforsuccess.org and 289 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://dressforsuccess.org/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://dressforsuccess.org/sitemap.xml.

AI search readiness

2 to fix53
  • robots.txt blocks 6 AI answer engine crawlers

    6 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • 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://dressforsuccess.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.

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

1 checks passed
  • Text is in the HTML

    Your server sends the page's text in the HTML (923 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

2 to fixGoogle 8887
  • 2 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://cloud.typography.com/6799492/758424/css/fonts.css' violates the following Content Security Polic…”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • 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

4 to fix57
  • 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 social proof

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

  • 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 206 words

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

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

3 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact”, “register” and “Learn more”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (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.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 22 other companies contacted

    Loading the homepage contacts 22 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 dressforsuccess.org, 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

Company

Headquarters
New York City

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on dressforsuccess.org, including 19 speed issues, 6 SEO issues and 4 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