baselang.com website review

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

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

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

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

9 images could be 17.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google CDN, Wistia and Intercom and others), adding 5.7 MB and 1.9 s of main-thread time.

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

Wistia costs a phone 395 ms of main-thread work and 4.2 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.

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

Google CDN costs a phone 569 ms of main-thread work and 741 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.

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

Intercom costs a phone 271 ms of main-thread work and 231 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.

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

Polyfills for old browsers add 44 KiB JavaScript that modern phones do not need.

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.

5 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 21.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Stop memorizing Spanish. Start speaking it.”.

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

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

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

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

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

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

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

Your homepage downloads 33.3 MB in 273 requests on a phone: images 19.5 MB (65), media 6.6 MB (1) and scripts 3.4 MB (102). Under 2 MB keeps phones on slow connections fast.

6 images weigh 17.7 MB together. On a phone connection a single image that size takes seconds.

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

7 images (18.0 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.

3 images are downloaded at several times the size a phone draws them, for example illustration-teachers-1.svg at 434 px wide, shown at 104 px. Resized copies would save about 193 KiB.

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

Certain ARIA roles must be contained by particular parents: 2 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

Some list items are not inside a list.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

Elements with visible text labels do not have matching accessible names. (6 elements).

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

The homepage links to 30 pages on baselang.com and 5 external pages.

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.

/accessibility-statement has no meta description, so Google writes the search snippet from whatever text it finds.

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

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56169520&tm=gtm002&Ver=2&mid=0216ee42-730d-4531-bb5f-c78e5174005b&bo=1&sid=8d8f70b0d3cc11f1a1f5455123d165d8&vid=8d8fc3b0d3cc11f18210cb9f75dc6a2c&vids=1&msclkid=N&pi=91.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Large scripts ship without source maps.

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

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.

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

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

Social proof on the homepage: “over 20,000 students”. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

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

The homepage carries about 1,165 words of visible text.

DMARC is set to p=none, so mail pretending to be baselang.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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Meta Pixel, Microsoft Ads and Microsoft Clarity and 3 mores (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.

Opening the homepage sets 26 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 51 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.