Website review, no card needed
inventorythai.com website review
Visit site (opens in a new tab)Reviewed 9 November 202639 issues · 69 checks
This review found 39 issues worth fixing on inventorythai.com, 17 of them high impact, across 69 checks. The most urgent: use efficient cache lifetimes. 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
72CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 911 ms |
| May 23, 2026 | 895 ms |
| May 30, 2026 | 875 ms |
| Jun 6, 2026 | 852 ms |
| Jun 13, 2026 | 872 ms |
| Jun 20, 2026 | 878 ms |
| Jun 27, 2026 | 921 ms |
| Jul 4, 2026 | 936 ms |
| Jul 11, 2026 | 946 ms |
| Jul 18, 2026 | 977 ms |
| Jul 25, 2026 | 963 ms |
| Aug 1, 2026 | 964 ms |
| Aug 8, 2026 | 974 ms |
| Aug 15, 2026 | 957 ms |
| Aug 22, 2026 | 965 ms |
| Aug 29, 2026 | 965 ms |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 963 ms |
| Sep 19, 2026 | 915 ms |
| Sep 26, 2026 | 875 ms |
| Oct 3, 2026 | 807 ms |
| Oct 10, 2026 | 864 ms |
| Oct 17, 2026 | 1.0 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 95 ms |
| May 23, 2026 | 94 ms |
| May 30, 2026 | 94 ms |
| Jun 6, 2026 | 95 ms |
| Jun 13, 2026 | 98 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 107 ms |
| Jul 4, 2026 | 113 ms |
| Jul 11, 2026 | 113 ms |
| Jul 18, 2026 | 116 ms |
| Jul 25, 2026 | 124 ms |
| Aug 1, 2026 | 123 ms |
| Aug 8, 2026 | 125 ms |
| Aug 15, 2026 | 118 ms |
| Aug 22, 2026 | 114 ms |
| Aug 29, 2026 | 111 ms |
| Sep 5, 2026 | 106 ms |
| Sep 12, 2026 | 105 ms |
| Sep 19, 2026 | 104 ms |
| Sep 26, 2026 | 114 ms |
| Oct 3, 2026 | 114 ms |
| Oct 10, 2026 | 116 ms |
| Oct 17, 2026 | 114 ms |
| Oct 24, 2026 | 104 ms |
| Oct 31, 2026 | 101 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
0.6 s
1.2 s
1.8 s
2.3 s
2.9 s
3.5 s
4.1 s
4.7 s
Speed
Use efficient cache lifetimes
3.3 s · 4.1 MB61 files are served with short cache lifetimes, so returning visitors download them again (4.1 MB).
Render-blocking requests
4.5 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.5 s.
Reduce unused CSS
3.0 s · 541 KiBAbout 541 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Font display
1.6 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.6 s).
Improve image delivery
350 ms · 1.8 MB16 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
371 KiBAbout 371 KiB of JavaScript is downloaded but never used on this page.
3 third-party services on the page
3 third-party services load with your homepage (Google Tag Manager, Google Analytics and LINE Corporation), adding 311 KiB and 188 ms of main-thread time.
Minify CSS
160 ms · 36 KiB36 KiB could be saved by minifying CSS.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 136 ms. During a long task the page ignores taps.
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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 188 ms of it running JavaScript. That is comfortably low.
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.
First Contentful Paint: 4.6 s
4.6 sThe first text or image appears after 4.6 s on a phone. Good is under 1.8 s.
Time to Interactive: 10.9 s
10.9 sThe page becomes fully interactive after 10.9 s. Good is under 3.8 s.
Largest Contentful Paint: 5.2 s
5.2 sYour largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) got 31% slower for real visitors
+31%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 864 ms
864 msReal visitors wait 864 ms for your server to start answering (75th percentile). Good is under 800 ms.
48 images without width and height
48 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 95 ms to 101 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 101 ms
101 msReal visitors wait 101 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 61 ms
61 msScripts block the page for only 61 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.4 MB in 65 requests
4.4 MBYour homepage downloads 4.4 MB in 65 requests on a phone: images 3.0 MB (44), scripts 630 KiB (10) and stylesheets 562 KiB (7). Under 2 MB keeps phones on slow connections fast.
19 images far larger than shown
1.4 MB19 images are downloaded at several times the size a phone draws them, for example 12.png at 1,534 px wide, shown at 366 px. Resized copies would save about 1.4 MB.
20 images in older formats
20 images (2.7 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.
21 images below the first screen load straight away
21 images further down the page (2.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.3 g of CO₂ per visit
1.26 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.26 g of CO₂e: 150.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
18 links without text
18 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
29 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 29 passed and 6 failed. 1 more need a person to judge. 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 long (203 characters)
Your title is 203 characters, so Google will cut it off around 60: “ระบบเบิกวัสดุ ระบบยืมคืนอุปกรณ์ โปรแกรมเบิกวัสดุ โปรแกรมยืมคืนอุปกรณ์ โปรแกรมคลังวัสดุ ระ…”.
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 (180 characters)
Your meta description is 180 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://inventorythai.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at inventorythai.com/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
19 internal links, 4 external
The homepage links to 19 pages on inventorythai.com and 4 external pages.
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://inventorythai.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.
1 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Best practices
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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 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 52 words
The homepage has only about 52 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.
1 checks passed
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
2 trackers load before any consent
2Before 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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
3 other companies contacted
Loading the homepage contacts 3 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 inventorythai.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Bootstrap
- Analytics
- Google Analytics
- Hosting
- DigitalOcean
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on inventorythai.com, including 15 speed issues, 8 SEO issues and 5 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.