cell-ed.com website review

About 503 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

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

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

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

4 images could be 649 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.

3 third-party services load with your homepage (Squarespace, sqspcdn.com and squarespace-cdn.com), adding 2.3 MB and 427 ms of main-thread time.

Squarespace costs a phone 411 ms of main-thread work and 1.1 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.

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

squarespace-cdn.com costs a phone 0 ms of main-thread work and 1.1 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.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

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

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

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.

Your homepage downloads 2.5 MB in 68 requests on a phone: scripts 1.1 MB (37), images 1,012 KiB (14) and stylesheets 166 KiB (10). Under 2 MB keeps phones on slow connections fast.

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

Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

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

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

Your title is only 7 characters: “Cell-Ed”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/69c50f951a134d54994…”.

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

The homepage links to 49 pages on cell-ed.com and 5 external pages.

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.

There is no /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.

/how-it-works and /our-solution all use the title “How It Works — Cell-Ed”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/how-it-works, /our-community, /impact, /about-us, /contact-us and /course-catalog and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example /our-solution, whose canonical is /how-it-works. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/academic-skills has no <h1> headline, so visitors and search engines get no clear main topic.

/course-catalog, /academic-skills, /work-skills and /courses 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.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/69c50f951a134d54994796f0/72/5c5a…”.

1 link to other sites is dead, for example https://login.portal.cell-ed.com/login?client_id=5ntu9u025s39s2bh7r7a23ikuk&response_type=code&redirect_uri=https://portal.cell-ed.com (404).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

cell-ed.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

cell-ed.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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 local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

DMARC is set to p=none, so mail pretending to be cell-ed.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Opening the homepage sets 3 cookies (measured from a US location before any click).

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.

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