Website review, no card needed

aiesec.lk logo

aiesec.lk website review

Visit site (opens in a new tab)Reviewed 30 October 202631 issues · 74 checks

This review found 31 issues worth fixing on aiesec.lk, 7 of them high impact, across 74 checks. The most urgent: page weight: 15.7 MB in 50 requests. 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
3.0 s2.0 sMay 9Oct 242.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.6 s
May 16, 20262.6 s
May 23, 20262.6 s
May 30, 20262.6 s
Jun 6, 20262.6 s
Jun 13, 20262.9 s
Jun 20, 20262.4 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.3 s
Aug 1, 20262.2 s
Aug 8, 20262.1 s
Aug 15, 20262.2 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
298 ms139 msMay 9Oct 24215 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026157 ms
May 16, 2026191 ms
May 30, 2026280 ms
Jun 20, 2026206 ms
Jun 27, 2026207 ms
Jul 4, 2026208 ms
Jul 11, 2026207 ms
Jul 25, 2026236 ms
Aug 1, 2026210 ms
Aug 8, 2026226 ms
Aug 15, 2026218 ms
Aug 22, 2026197 ms
Aug 29, 2026194 ms
Sep 5, 2026194 ms
Sep 19, 2026185 ms
Sep 26, 2026196 ms
Oct 3, 2026207 ms
Oct 10, 2026207 ms
Oct 17, 2026215 ms
Oct 24, 2026215 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 aiesec.lk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aiesec.lk at 0.6 s0.6 s
  2. aiesec.lk at 1.2 s1.2 s
  3. aiesec.lk at 1.8 s1.8 s
  4. aiesec.lk at 2.4 s2.4 s
  5. aiesec.lk at 2.9 s2.9 s
  6. aiesec.lk at 3.5 s3.5 s
  7. aiesec.lk at 4.1 s4.1 s
  8. aiesec.lk at 4.7 s4.7 s

Speed

5 to fix61
  • Improve image delivery

    3.4 MB

    1 image could be 3.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 61

    61/100

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

  • Reduce unused JavaScript

    450 ms · 78 KiB

    About 78 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Render-blocking requests

    500 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 500 ms.

  • 3 long tasks on the main thread

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

  • Use efficient cache lifetimes

    150 ms · 6 KiB

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

  • Legacy JavaScript

    24 KiB

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (Cloudflare), adding 10 KiB and 6 ms of main-thread time.

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

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

10 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 14.7 s

    14.7 s

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

  • Time to Interactive: 15.8 s

    15.8 s

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

  • Speed Index: 10.7 s

    10.7 s

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

  • Real-user INP: 202 ms

    202 ms

    Real visitors wait 202 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

    +24%

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 897 ms

    897 ms

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • 12 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -7%

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

4 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Total Blocking Time: 172 ms

    172 ms

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

2 to fix60
  • Page weight: 15.7 MB in 50 requests

    15.7 MB

    Your homepage downloads 15.7 MB in 50 requests on a phone: media 10.2 MB (3), images 5.1 MB (19) and scripts 340 KiB (16). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    45 KiB

    1 image is downloaded at several times the size a phone draws it, for example Aiesec-Black-Logo.avif at 1,265 px wide, shown at 234 px. Resized copies would save about 45 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (65 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 4.5 g of CO₂ per visit

    4.45 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

4 to fix79
  • 11 buttons without a name

    11 buttons have no accessible name, so screen readers announce just “button”.

  • 11 tap targets too small

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

  • 5 text elements with low contrast

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

  • 4 links without text

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

1 checks passed
  • Every image has alt text

    All 93 images in the HTML carry an alt attribute.

SEO

5 to fixGoogle 9280
  • No structured data

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

  • 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 (171 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.aiesec.lk/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

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

  • 9 internal links, 7 external

    The homepage links to 9 pages on aiesec.lk and 7 external pages.

3 checks passed
  • One H1 headline

    Your main headline reads: “Youth LeadershipThat Transforms”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “AIESEC in Sri Lanka | Youth Leadership & Global Opportunities”.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • 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://www.aiesec.lk/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 (610 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 5 pages share 2 titles

    / and https://www.aiesec.lk/privacy-and-cookie-policy all use the title “AIESEC in Sri Lanka | Youth Leadership & Global Opportunities”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages share a meta description

    https://www.aiesec.lk/partner/mas, https://www.aiesec.lk/partner/cargills and https://www.aiesec.lk/partner/ceylinco-life use the same meta description. A description written for each page earns more clicks.

  • 1 page with very little text

    https://www.aiesec.lk/privacy-and-cookie-policy 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.

  • 5 internal pages checked

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

6 checks passed
  • Linked pages load

    All 5 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 5 pages that loaded have a meta description.

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

Best practices

1 to fixGoogle 9692
  • 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”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 605 words of copy

    The homepage carries about 605 words of visible text.

5 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact”, “Sign Up” and “How can I join AIESEC?”.

  • 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: 61 customer or partner logos and “1800+ Active Members”.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

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

  • 1 other company contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

Framework
Next.js
Hosting
Vercel

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on aiesec.lk, including 15 speed issues, 5 SEO issues and 1 conversion gap. 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