Website review, no card needed

ed.careers logo

ed.careers website review

Visit site (opens in a new tab)Reviewed 20 November 202632 issues · 78 checks

This review found 32 issues worth fixing on ed.careers, 8 of them high impact, across 78 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.6 s1.2 sMay 30Nov 71.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.5 s
Jun 6, 20261.4 s
Jun 13, 20261.3 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.3 s
Jul 25, 20261.2 s
Aug 1, 20261.3 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.4 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.4 s
Oct 10, 20261.5 s
Oct 17, 20261.3 s
Oct 24, 20261.4 s
Oct 31, 20261.2 s
Nov 7, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
107 ms84 msMay 30Oct 24103 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202689 ms
Jun 6, 202688 ms
Jun 13, 202692 ms
Jun 20, 202695 ms
Jun 27, 202695 ms
Jul 4, 202695 ms
Jul 11, 2026102 ms
Jul 18, 2026103 ms
Jul 25, 2026103 ms
Aug 1, 2026104 ms
Aug 8, 202698 ms
Aug 15, 202696 ms
Aug 22, 202696 ms
Aug 29, 202694 ms
Sep 5, 202694 ms
Sep 12, 202688 ms
Sep 19, 202687 ms
Sep 26, 202687 ms
Oct 3, 202687 ms
Oct 10, 202695 ms
Oct 17, 202695 ms
Oct 24, 2026103 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 ed.careers (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix54
  • Reduce unused JavaScript

    9.2 s · 1.2 MB

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

  • Improve image delivery

    1.4 s · 435 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and Other Google APIs/SDKs and others), adding 4.9 MB and 707 ms of main-thread time.

  • Mobile performance score: 54

    54/100

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

  • YouTube adds 606 ms

    606 ms

    YouTube costs a phone 606 ms of main-thread work and 1.9 MB 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.

  • Render-blocking requests

    300 ms

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

  • WordPress adds 7 ms

    7 ms

    WordPress costs a phone 7 ms of main-thread work and 2.5 MB 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.

  • Use efficient cache lifetimes

    197 KiB

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

  • Reduce unused CSS

    150 ms · 47 KiB

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

  • 6 long tasks on the main thread

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

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 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.

2 checks passed
  • Main-thread work: 1.7 s

    A phone's processor spends 1.7 s on main-thread work while loading, 988 ms of it running JavaScript. That is comfortably low.

  • Server response: 52 ms

    52 ms

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

Core Web Vitals

4 to fix65
  • First Contentful Paint: 12.8 s

    12.8 s

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

  • Largest Contentful Paint: 21.7 s

    21.7 s

    Your largest element takes 21.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WORK FOR A COMPANY AT THE TOP OF ITS GAME Don’t just find a…”.

  • Time to Interactive: 21.8 s

    21.8 s

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

  • Speed Index: 12.8 s

    12.8 s

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

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

    +12%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • Largest content (LCP) got 18% faster for real visitors

    -18%

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

  • Total Blocking Time: 156 ms

    156 ms

    Scripts block the page for only 156 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

3 to fix53
  • Page weight: 5.7 MB in 75 requests

    5.7 MB

    Your homepage downloads 5.7 MB in 75 requests on a phone: media 2.0 MB (1), scripts 1.9 MB (18) and images 922 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 4 images below the first screen load straight away

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

  • 1 image far larger than shown

    3 KiB

    1 image is downloaded at several times the size a phone draws it, for example locations-1.gif at 1,080 px wide, shown at 358 px. Resized copies would save about 3 KiB.

  • 1 image in older formats

    1 image (251 KiB) 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.6 g of CO₂ per visit

    1.63 g

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

Accessibility

5 to fixGoogle 9795
  • All page content should be contained by landmarks (29 elements)

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

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

4 to fixGoogle 9282
  • Title is short (19 characters)

    Your title is only 19 characters: “Edfinancial Careers”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No canonical URL

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

  • Meta description is long (347 characters)

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

  • 3 links with vague text

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

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 24 internal links, 16 external

    The homepage links to 24 pages on ed.careers and 16 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “WORK FOR A COMPANY AT THE TOP OF ITS GAME”.

  • Structured data in place

    Structured data found: Organization and WebSite.

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

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

  • llms.txt published

    The site publishes https://ed.careers/llms.txt (1 KiB, 3 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix88
  • 1 page without a meta description

    https://ed.careers/currentopenings has no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages share a meta description

    https://ed.careers/what-we-do, https://ed.careers/who-we-are, https://ed.careers/benefits, https://ed.careers/events, https://ed.careers/faq and https://ed.careers/pathways-job-fair-february-2026 and 1 other use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://ed.careers/currentopenings has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://ed.careers/currentopenings 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.

  • 8 internal pages checked

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

5 checks passed
  • Linked pages load

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7785
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 small tap targets

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

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

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

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

    The homepage carries about 640 words of visible text.

4 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Apply now”, “Learn More” and “Apply Now”.

  • 1 short form

    A short form (4 fields at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies, 1 of them by other companies (measured from a US location before any click).

  • 18 other companies contacted

    Loading the homepage contacts 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

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 ed.careers, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
WordPress
Analytics
Google Analytics
Hosting
WordPress.com

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on ed.careers, including 11 speed issues, 4 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