jobtest.vn website review

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

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

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

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

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

35 images could be 3.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Facebook and cmctelecom.vn and others), adding 2.3 MB and 1.4 s of main-thread time.

Google Tag Manager costs a phone 806 ms of main-thread work and 715 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.

Facebook costs a phone 285 ms of main-thread work and 232 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.

cmctelecom.vn costs a phone 172 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.

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

The page has 1,514 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

45 KiB could be saved by minifying JavaScript.

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

About 38 KiB of CSS is downloaded but never applied on this page.

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.

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 20.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

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

The layout shifts by 0.17 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Your homepage downloads 7.0 MB in 185 requests on a phone: images 5.3 MB (105), scripts 1.4 MB (40) and fonts 152 KiB (5). Under 2 MB keeps phones on slow connections fast.

1728551385-987.png weighs 729 KiB. On a phone connection a single image that size takes seconds.

15 images are downloaded at several times the size a phone draws them, for example 1668658306-287.jpg at 941 px wide, shown at 255 px. Resized copies would save about 724 KiB.

27 images (4.3 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.

29 images further down the page (3.6 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 1.98 g of CO₂e: 238.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

Some list items are not inside a list.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

23 images have no alt text, which hurts accessibility and image search.

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

11 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

Your title is 81 characters, so Google will cut it off around 60: “JobTest | Nền tảng hướng nghiệp và Đánh giá năng lực trực tuyến hàng đầu Việt Nam”.

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

2 links have no real href, so search engines can't follow them.

The homepage links to 57 pages on jobtest.vn and 22 external pages.

https://jobtest.vn/user/test/test-buy, https://jobtest.vn/user/test/test-assessor, https://jobtest.vn/user/my-cvs, https://jobtest.vn/user/applied-jobs and https://jobtest.vn/user/save-jobs have no <title>, so Google invents the link text in results.

https://jobtest.vn/user, https://jobtest.vn/user/test/test-buy, https://jobtest.vn/user/orders, https://jobtest.vn/user/test/test-assessor, https://jobtest.vn/user/my-cvs and https://jobtest.vn/user/applied-jobs and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://jobtest.vn/user, https://jobtest.vn/user/test/test-buy, https://jobtest.vn/user/orders, https://jobtest.vn/user/test/test-assessor and https://jobtest.vn/user/save-jobs have no <h1> headline, so visitors and search engines get no clear main topic.

https://jobtest.vn/coming-soon 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.

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

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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.

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

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