Website review, no card needed
aiesec.or.id website review
Visit site (opens in a new tab)Reviewed 26 October 202642 issues · 65 checks
This review found 42 issues worth fixing on aiesec.or.id, 16 of them high impact, across 65 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
56FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 6.4 s |
| May 16, 2026 | 6.5 s |
| May 23, 2026 | 6.3 s |
| May 30, 2026 | 6.3 s |
| Jun 6, 2026 | 6.4 s |
| Jun 13, 2026 | 6.4 s |
| Jun 20, 2026 | 6.5 s |
| Jun 27, 2026 | 6.5 s |
| Jul 4, 2026 | 6.6 s |
| Jul 11, 2026 | 6.3 s |
| Jul 18, 2026 | 6.1 s |
| Jul 25, 2026 | 6.0 s |
| Aug 1, 2026 | 5.7 s |
| Aug 8, 2026 | 5.7 s |
| Aug 15, 2026 | 5.6 s |
| Aug 22, 2026 | 5.7 s |
| Aug 29, 2026 | 5.7 s |
| Sep 5, 2026 | 5.6 s |
| Sep 12, 2026 | 5.7 s |
| Sep 19, 2026 | 5.8 s |
| Sep 26, 2026 | 6.2 s |
| Oct 3, 2026 | 6.6 s |
| Oct 10, 2026 | 6.6 s |
| Oct 17, 2026 | 6.8 s |
| Oct 24, 2026 | 6.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 182 ms |
| May 16, 2026 | 196 ms |
| May 23, 2026 | 204 ms |
| May 30, 2026 | 215 ms |
| Jun 6, 2026 | 218 ms |
| Jun 13, 2026 | 214 ms |
| Jun 20, 2026 | 221 ms |
| Jun 27, 2026 | 221 ms |
| Jul 4, 2026 | 231 ms |
| Jul 11, 2026 | 223 ms |
| Jul 18, 2026 | 209 ms |
| Jul 25, 2026 | 198 ms |
| Aug 1, 2026 | 205 ms |
| Aug 8, 2026 | 211 ms |
| Aug 15, 2026 | 214 ms |
| Aug 22, 2026 | 213 ms |
| Aug 29, 2026 | 208 ms |
| Sep 5, 2026 | 204 ms |
| Sep 12, 2026 | 202 ms |
| Sep 19, 2026 | 196 ms |
| Sep 26, 2026 | 199 ms |
| Oct 3, 2026 | 190 ms |
| Oct 10, 2026 | 183 ms |
| Oct 17, 2026 | 172 ms |
| Oct 24, 2026 | 171 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
How it loaded on a phone
2.0 s
4.0 s
6.0 s
8.1 s
10.1 s
12.1 s
14.1 s
16.1 s
Speed
Reduce unused JavaScript
2.7 s · 901 KiBAbout 901 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Render-blocking requests
1.9 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Mobile performance score: 41
41/100Your mobile performance score is 41 (desktop: 76). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.4 s
A phone's processor spends 4.4 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5 third-party services on the page
5 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Fonts and others), adding 1.2 MB and 831 ms of main-thread time.
Google CDN adds 752 ms
752 msGoogle CDN costs a phone 752 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.
Reduce unused CSS
630 ms · 145 KiBAbout 145 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 630 ms faster on a phone.
Use efficient cache lifetimes
402 KiB3 files are served with short cache lifetimes, so returning visitors download them again (402 KiB).
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 228 ms. During a long task the page ignores taps.
Phones get a much slower page than desktops
Desktop scores 76 but mobile only 41. 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.
Document request latency
5 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user LCP: 6.3 s
6.3 sReal visitors wait 6.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.6 s
5.6 sReal visitors see the first content after 5.6 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 11.7 s
11.7 sYour largest element takes 11.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Empowering Leaders, Transforming the World”. Most of its time is element render delay (13.7 s).
Speed Index: 25.8 s
25.8 sVisually, the page fills in at 25.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.9 s
5.9 sThe first text or image appears after 5.9 s on a phone. Good is under 1.8 s.
Time to Interactive: 16.6 s
16.6 sThe page becomes fully interactive after 16.6 s. Good is under 3.8 s.
Real-user INP: 210 ms
210 msReal visitors wait 210 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 867 ms
867 msReal visitors wait 867 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 569 ms
569 msScripts block taps and scrolling for 569 ms in total while the page loads. Good is under 200 ms.
19 images without width and height
19 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 182 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 6.4 s to 6.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.5 MB in 116 requests
3.5 MBYour homepage downloads 3.5 MB in 116 requests on a phone: scripts 1.8 MB (31), other files 873 KiB (52) and images 405 KiB (20). Under 2 MB keeps phones on slow connections fast.
About 1.0 g of CO₂ per visit
0.99 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.99 g of CO₂e: 118.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
16 text elements with low contrast
16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
1 checks passed
5 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 8 WCAG 2.2 A/AA and best-practice rules on the phone render: 5 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (15 characters)
Your title is only 15 characters: “AIESEC | AIESEC”. Between 30 and 65 characters leaves room to say what you do and for whom.
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.
No robots.txt
There is no robots.txt at aiesec.or.id/robots.txt, the first file search crawlers ask for.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
Invalid hreflang
Your hreflang tags are invalid, so Google may show the wrong language version.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
3 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “Activate your leadership by taking part in one of our programs abroad, in your city, or virtually. Start your leadershi…”.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
XML sitemap found
Your XML sitemap is reachable at https://aiesec.or.id/sitemap.xml.
AI search readiness
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://aiesec.or.id/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.
Best practices
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
Only about 0 words
The homepage has only about 0 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
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.or.id, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Nuxt
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on aiesec.or.id, including 19 speed issues, 9 SEO issues and 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.