youngontop.com website review

54 images could be 9.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.8 s faster on a phone.

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

201 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).

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

About 220 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

7 third-party services load with your homepage (Google Tag Manager, datatables.net and Cloudflare and others), adding 432 KiB and 163 ms of main-thread time.

3 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 22 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.

2 KiB could be saved by minifying CSS.

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 visitors wait 5.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your largest element takes 44.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “YOT telah menjangkau jutaan anak muda di 1.000+ kampus dan …”.

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

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

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

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

32 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-17, real Chrome visitors' tap response (inp) went from 171 ms to 175 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.3 MB in 222 requests on a phone: images 10.8 MB (66), scripts 997 KiB (70) and stylesheets 403 KiB (73). Under 2 MB keeps phones on slow connections fast.

37 images are downloaded at several times the size a phone draws them, for example Dania-scaled.jpeg at 2,038 px wide, shown at 99 px. Resized copies would save about 6.1 MB.

8 images weigh 5.4 MB together. On a phone connection a single image that size takes seconds.

40 images (9.9 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.

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

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

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

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

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

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 on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 19 characters: “Home - Young On Top”. Between 30 and 65 characters leaves room to say what you do and for whom.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 41 pages on youngontop.com and 8 external pages.

There is no https://youngontop.com/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.

https://youngontop.com/about-us, https://youngontop.com/our-program, https://youngontop.com/events, https://youngontop.com/articles, https://youngontop.com/career and https://youngontop.com/store and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://youngontop.com/about-us, https://youngontop.com/our-program, https://youngontop.com/events, https://youngontop.com/articles, https://youngontop.com/career and https://youngontop.com/store and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://youngontop.com/contact-us 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.

https://youngontop.com/store took over 3 s to send its HTML from our server.

We fetched 15 pages linked from your homepage (of 19 found) and read each the way a search engine does.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cloudflare.com/?ver=4.0.13' from origin 'https://youngontop.com' has been blocked …”.

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

Large scripts ship without source maps.

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

Social proof on the homepage: 58 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

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

The homepage carries about 550 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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 9 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.