Website review, no card needed

avedafi.edu logo

avedafi.edu website review

Visit site (opens in a new tab)Reviewed 22 October 202639 issues · 91 checks

This review found 39 issues worth fixing on avedafi.edu, 14 of them high impact, across 91 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
1.1 s922 msMay 2Oct 17942 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.0 s
May 9, 20261.0 s
May 16, 20261.0 s
May 23, 20261.0 s
May 30, 2026989 ms
Jun 6, 20261.0 s
Jun 13, 2026974 ms
Jun 20, 2026960 ms
Jun 27, 2026975 ms
Jul 4, 2026964 ms
Jul 11, 2026976 ms
Jul 18, 2026995 ms
Jul 25, 2026990 ms
Aug 1, 2026987 ms
Aug 8, 2026990 ms
Aug 15, 20261.0 s
Aug 22, 2026997 ms
Aug 29, 2026984 ms
Sep 5, 2026950 ms
Sep 12, 2026937 ms
Sep 19, 2026947 ms
Sep 26, 2026951 ms
Oct 3, 2026956 ms
Oct 10, 2026945 ms
Oct 17, 2026942 ms
Real-visitor tap response (INP)75th percentile, phones
271 ms131 msMay 2Oct 17255 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026150 ms
May 9, 2026152 ms
May 16, 2026154 ms
May 23, 2026148 ms
May 30, 2026147 ms
Jun 6, 2026152 ms
Jun 13, 2026154 ms
Jun 20, 2026157 ms
Jun 27, 2026159 ms
Jul 4, 2026154 ms
Jul 11, 2026152 ms
Jul 18, 2026153 ms
Jul 25, 2026152 ms
Aug 1, 2026150 ms
Aug 8, 2026162 ms
Aug 15, 2026179 ms
Aug 22, 2026187 ms
Aug 29, 2026204 ms
Sep 5, 2026212 ms
Sep 12, 2026214 ms
Sep 19, 2026227 ms
Sep 26, 2026236 ms
Oct 3, 2026238 ms
Oct 10, 2026246 ms
Oct 17, 2026255 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 avedafi.edu (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

12 to fix35
  • Use efficient cache lifetimes

    2.7 s · 762 KiB

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

  • Improve image delivery

    1.6 s · 495 KiB

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

  • Reduce unused JavaScript

    1.6 s · 376 KiB

    About 376 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.8 s

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

  • Mobile performance score: 35

    35/100

    Your mobile performance score is 35 (desktop: 84). 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 (Google Tag Manager, Facebook and TikTok and others), adding 1.5 MB and 1.1 s of main-thread time.

  • Reduce unused CSS

    900 ms · 118 KiB

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

  • Google Tag Manager adds 386 ms

    386 ms

    Google Tag Manager costs a phone 386 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.

  • Facebook adds 383 ms

    383 ms

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

  • 9 long tasks on the main thread

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

  • Main-thread work: 3.0 s

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

  • apple-mapkit.com adds 0 ms

    0 ms

    apple-mapkit.com costs a phone 0 ms of main-thread work and 523 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 · 21 KiB

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

  • Font display

    150 ms

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

  • Phones get a much slower page than desktops

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

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

    1 ms

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

Core Web Vitals

7 to fix100
  • First Contentful Paint: 10.5 s

    10.5 s

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

  • Largest Contentful Paint: 18.1 s

    18.1 s

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

  • Time to Interactive: 18.8 s

    18.8 s

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

  • Speed Index: 10.5 s

    10.5 s

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

  • Total Blocking Time: 921 ms

    921 ms

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

  • Tap response (INP) got 66% slower for real visitors

    +66%

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

  • 7 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

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

    1.6 s

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

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

    1.2 s

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

  • Real-user TTFB: 592 ms

    592 ms

    Real visitors wait 592 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

3 to fix68
  • Page weight: 3.1 MB in 58 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 58 requests on a phone: scripts 2.1 MB (12), images 813 KiB (22) and stylesheets 147 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 6 images in older formats

    6 images (522 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.

  • 6 images below the first screen load straight away

    6 images further down the page (522 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.9 g of CO₂ per visit

    0.88 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

6 to fixGoogle 8792
  • Unlabelled dropdowns

    2 dropdowns have no label.

  • Hidden but focusable

    12 elements hidden from screen readers can still receive keyboard focus.

  • 11 text elements with low contrast

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

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

  • 12 links without text

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

  • 9 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 8 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

3 to fixGoogle 9289
  • 14 H1 headlines

    There are 14 <h1> headlines (“Do What You Love”, “Cosmetology” and “Esthetics”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 8 links with vague text

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

  • No X (Twitter) card tag

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

  • 69 internal links, 37 external

    The homepage links to 69 pages on avedafi.edu and 37 external pages.

6 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Your salon spa career begins here! Start your new career in under 13 months. Attend an award-winning cosmetology & esth…”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Nurtur Aveda Institutes - Cosmetology School - Beauty Academy”.

  • Structured data in place

    Structured data found: EducationalOrganization.

  • 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://avedafi.edu/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://avedafi.edu/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 (760 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix93
  • 1 page without a meta description

    https://avedafi.edu/events has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://avedafi.edu/salon-services/appointments and https://avedafi.edu/salon-services use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 29 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.

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

Best practices

1 to fixGoogle 7797
  • 1 third-party cookie

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

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • 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.

  • A 9-field form

    Your longest form asks for 9 fields (7 required). Every extra field lowers completion.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

    The homepage carries about 707 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “APPLY NOW” and “BOOK APPOINTMENT”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Apply Now”, “Book Appointment” and “Join Our Team”.

  • Analytics in place

    Analytics detected: Google Analytics, Meta Pixel and TikTok Pixel.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 13 cookies set on arrival

    13

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

  • 19 other companies contacted

    Loading the homepage contacts 19 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 avedafi.edu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on avedafi.edu, including 19 speed issues, 3 SEO issues and 3 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