Website review, no card needed

dpu.ac.th logo

dpu.ac.th website review

Visit site (opens in a new tab)Reviewed 19 October 202652 issues · 91 checks

This review found 52 issues worth fixing on dpu.ac.th, 21 of them high impact, across 91 checks. The most urgent: use efficient cache lifetimes. 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
4.1 s2.0 sApr 25Oct 102.2 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20263.6 s
May 2, 20263.7 s
May 9, 20263.8 s
May 16, 20263.8 s
May 23, 20263.8 s
May 30, 20263.5 s
Jun 6, 20263.2 s
Jun 13, 20263.0 s
Jun 20, 20262.7 s
Jun 27, 20262.6 s
Jul 4, 20262.7 s
Jul 11, 20262.7 s
Jul 18, 20262.7 s
Jul 25, 20262.6 s
Aug 1, 20262.5 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.5 s
Sep 5, 20262.6 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.4 s
Oct 3, 20262.3 s
Oct 10, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
272 ms246 msApr 25Oct 10258 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026256 ms
May 2, 2026266 ms
May 9, 2026265 ms
May 16, 2026262 ms
May 23, 2026259 ms
May 30, 2026251 ms
Jun 6, 2026257 ms
Jun 13, 2026259 ms
Jun 20, 2026259 ms
Jun 27, 2026261 ms
Jul 4, 2026254 ms
Jul 11, 2026251 ms
Jul 18, 2026250 ms
Jul 25, 2026249 ms
Aug 1, 2026252 ms
Aug 8, 2026257 ms
Aug 15, 2026258 ms
Aug 22, 2026260 ms
Aug 29, 2026263 ms
Sep 5, 2026269 ms
Sep 12, 2026264 ms
Sep 19, 2026264 ms
Sep 26, 2026262 ms
Oct 3, 2026256 ms
Oct 10, 2026258 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 dpu.ac.th (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dpu.ac.th at 0.7 s0.7 s
  2. dpu.ac.th at 1.4 s1.4 s
  3. dpu.ac.th at 2.0 s2.0 s
  4. dpu.ac.th at 2.7 s2.7 s
  5. dpu.ac.th at 3.4 s3.4 s
  6. dpu.ac.th at 4.1 s4.1 s
  7. dpu.ac.th at 4.8 s4.8 s
  8. dpu.ac.th at 5.4 s5.4 s

Speed

12 to fix33
  • Use efficient cache lifetimes

    4.4 s · 12.1 MB

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

  • Improve image delivery

    1.8 s · 6.3 MB

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

  • Reduce unused JavaScript

    5.3 s · 1.0 MB

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

  • Mobile performance score: 33

    33/100

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

  • Main-thread work: 5.0 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Hotjar and others), adding 2.5 MB and 1.9 s of main-thread time.

  • Google Tag Manager adds 993 ms

    993 ms

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

  • Render-blocking requests

    800 ms

    14 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

  • 20 long tasks on the main thread

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

  • Facebook adds 252 ms

    252 ms

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

  • pdpanetka.com adds 96 ms

    96 ms

    pdpanetka.com costs a phone 96 ms of main-thread work and 828 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.

  • 1,523 HTML elements

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

  • Legacy JavaScript

    150 ms · 33 KiB

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

  • Minify JavaScript

    100 KiB

    100 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    67 KiB

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

  • Font display

    50 ms

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

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

  • 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: 28 ms

    28 ms

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

Core Web Vitals

9 to fix33
  • 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: 4.1 s

    4.1 s

    Real visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Largest Contentful Paint: 25.0 s

    25.0 s

    Your largest element takes 25.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “DPU ม.เอกชน อันดับ1 เรียนจบได้งานจริง”.

  • Time to Interactive: 27.4 s

    27.4 s

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

  • Speed Index: 12.3 s

    12.3 s

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

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • First Contentful Paint: 4.1 s

    4.1 s

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

  • Real-user INP: 263 ms

    263 ms

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

  • 5 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -2%

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

5 checks passed
  • Real-user CLS: 0.09

    0.09

    For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 785 ms

    785 ms

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

  • Largest content (LCP) got 37% faster for real visitors

    -37%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

5 to fix18
  • Page weight: 16.2 MB in 195 requests

    16.2 MB

    Your homepage downloads 16.2 MB in 195 requests on a phone: images 10.6 MB (53), scripts 2.4 MB (65) and media 2.3 MB (2). Under 2 MB keeps phones on slow connections fast.

  • 8 images over 500 KB

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

  • 6 images far larger than shown

    1.5 MB

    6 images are downloaded at several times the size a phone draws them, for example d8330b3a-7f33-43fe-b59f-3cf43e1a75e5.jpg at 2,147 px wide, shown at 20 px. Resized copies would save about 1.5 MB.

  • 25 images in older formats

    25 images (10.4 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.

  • 16 images below the first screen load straight away

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

  • About 4.6 g of CO₂ per visit

    4.60 g

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

Accessibility

9 to fixGoogle 8086
  • 4 buttons without a name

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

  • Images must have alternative text (2 elements)

    Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

  • 8 text elements with low contrast

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

  • All page content should be contained by landmarks (14 elements)

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

  • Main landmark should not be contained in another landmark (6 elements)

    Main landmark should not be contained in another landmark: 6 elements on the page fail this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • 6 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Elements with visible text labels do not have matching accessible names.

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

1 checks passed
  • 35 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8372
  • No H1 headline

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

  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “หน้าแรก - Dhurakij Pundit University | มหาวิทยาลัยธุรกิจบัณฑิตย์ (DPU)”.

  • Meta description is short (60 characters)

    Your meta description is only 60 characters: “Dhurakij Pundit University (DPU) : มหาวิทยาลัยธุรกิจบัณฑิตย์”. 70 to 160 characters is enough to sell the click.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 5 links crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 36 internal links, 11 external

    The homepage links to 36 pages on dpu.ac.th and 11 external pages.

4 checks passed
  • Structured data in place

    Structured data found: CollegeOrUniversity.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.dpu.ac.th/sitemap-main.xml.

AI search readiness

1 to fix83
  • 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.dpu.ac.th/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.

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

Other pages

5 to fix67
  • 4 pages without a title

    https://www.dpu.ac.th/th/scholarship/bachelor, https://www.dpu.ac.th/th/scholarship/master, https://www.dpu.ac.th/th/course/finder/bachelor and https://www.dpu.ac.th/e-regis/regis.html have no <title>, so Google invents the link text in results.

  • 4 pages share 2 titles

    https://www.dpu.ac.th/th/tuition/master and https://www.dpu.ac.th/th/tuition/doctorate all use the title “อัตราค่าเทอมหลักสูตรปริญญาโท-เอก - Dhurakij Pundit University | มหาวิ…”, 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 without a meta description

    https://www.dpu.ac.th/th/scholarship/bachelor, https://www.dpu.ac.th/th/scholarship/master and https://www.dpu.ac.th/th/course/finder/bachelor have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages share a meta description

    https://www.dpu.ac.th/th/tuition/bachelor, https://www.dpu.ac.th/th/tuition/master, https://www.dpu.ac.th/th/tuition/doctorate, https://www.dpu.ac.th/th/announcement/promotions, https://www.dpu.ac.th/th/course/compare and https://www.dpu.ac.th/th/announcement/brochure-dpu and 5 others use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://www.dpu.ac.th/th/scholarship/bachelor, https://www.dpu.ac.th/th/scholarship/master and https://www.dpu.ac.th/th/student-life have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 pages with very little text

    https://www.dpu.ac.th/th/tuition/bachelor, https://www.dpu.ac.th/th/tuition/master, https://www.dpu.ac.th/th/tuition/doctorate, https://www.dpu.ac.th/th/scholarship/bachelor, https://www.dpu.ac.th/th/scholarship/master and https://www.dpu.ac.th/th/announcement/promotions and 9 others have 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.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 9687
  • 4 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were 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

3 to fix67
  • 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 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 63 words

    The homepage has only about 63 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.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “learn more about cookies”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Join Our Team”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 1 more (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.

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 cookies (measured from a US location before any click).

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

  • 26 other companies contacted

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

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 dpu.ac.th, 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
Analytics
Google Tag Manager

Company

Founded
1968
Headquarters
Lak Si

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on dpu.ac.th, including 21 speed issues, 5 SEO issues and 3 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

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