Website review, no card needed
ocean.co.th website review
Visit site (opens in a new tab)Reviewed 30 October 202643 issues · 84 checks
This review found 43 issues worth fixing on ocean.co.th, 20 of them high impact, across 84 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 197 ms |
| May 16, 2026 | 192 ms |
| May 23, 2026 | 192 ms |
| May 30, 2026 | 192 ms |
| Jun 6, 2026 | 190 ms |
| Jun 13, 2026 | 192 ms |
| Jun 20, 2026 | 192 ms |
| Jun 27, 2026 | 190 ms |
| Jul 4, 2026 | 189 ms |
| Jul 11, 2026 | 186 ms |
| Jul 18, 2026 | 183 ms |
| Jul 25, 2026 | 177 ms |
| Aug 1, 2026 | 174 ms |
| Aug 8, 2026 | 170 ms |
| Aug 15, 2026 | 169 ms |
| Aug 22, 2026 | 170 ms |
| Aug 29, 2026 | 169 ms |
| Sep 5, 2026 | 171 ms |
| Sep 12, 2026 | 170 ms |
| Sep 19, 2026 | 170 ms |
| Sep 26, 2026 | 170 ms |
| Oct 3, 2026 | 175 ms |
| Oct 10, 2026 | 187 ms |
| Oct 17, 2026 | 200 ms |
| Oct 24, 2026 | 213 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.1 s
1.7 s
2.2 s
2.8 s
3.4 s
3.9 s
4.5 s
Speed
Use efficient cache lifetimes
8.6 s · 4.2 MB50 files are served with short cache lifetimes, so returning visitors download them again (4.2 MB).
Render-blocking requests
4.2 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.2 s.
Reduce unused CSS
2.9 s · 573 KiBAbout 573 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.9 s faster on a phone.
Improve image delivery
1.6 s · 872 KiB8 images could be 872 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.
Google Tag Manager adds 1.0 s
1.0 sGoogle Tag Manager costs a phone 1.0 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1.7 MB and 1.6 s of main-thread time.
Reduce unused JavaScript
150 ms · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Font display
900 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 900 ms).
Main-thread work: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 191 ms. During a long task the page ignores taps.
Legacy JavaScript
167 KiBPolyfills for old browsers add 167 KiB JavaScript that modern phones do not need.
Document request latency
82 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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: 534 ms
534 msYour server sent the HTML in 534 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.
Largest Contentful Paint: 10.2 s
10.2 sYour largest element takes 10.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 29.2 s
29.2 sThe page becomes fully interactive after 29.2 s. Good is under 3.8 s.
Speed Index: 10.3 s
10.3 sVisually, the page fills in at 10.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.5 s
4.5 sThe first text or image appears after 4.5 s on a phone. Good is under 1.8 s.
Total Blocking Time: 751 ms
751 msScripts block taps and scrolling for 751 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 228 ms
228 msReal visitors wait 228 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 960 ms
960 msReal visitors wait 960 ms for your server to start answering (75th percentile). Good is under 800 ms.
16 images without width and height
16 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 197 ms to 213 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.085
0.085The layout barely moves while loading (CLS 0.085, good is under 0.1).
Images and page weight
Page weight: 5.8 MB in 118 requests
5.8 MBYour homepage downloads 5.8 MB in 118 requests on a phone: scripts 2.5 MB (35), images 1.8 MB (28) and fonts 751 KiB (8). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
1920x1080-(2).jpg weighs 623 KiB. On a phone connection a single image that size takes seconds.
10 images in older formats
10 images (1.8 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.
5 images below the first screen load straight away
5 images further down the page (625 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
120 KiB2 images are downloaded at several times the size a phone draws them, for example logo-oceanlife-2025-mobile.jpg at 492 px wide, shown at 50 px. Resized copies would save about 120 KiB.
About 1.6 g of CO₂ per visit
1.64 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.64 g of CO₂e: 197.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
18 text elements with low contrast
18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 38 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“” and “แบบประกันยอดนิยม”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
92 internal links, 20 external
The homepage links to 92 pages on ocean.co.th and 20 external pages.
6 checks passed
Meta description: 118 characters
Your meta description is 118 characters: “สนใจประกัน ประกัน ประกันสุขภาพ ประกันลดหย่อนภาษี ประกันอุบัติเหตุ ปรึกษาผู้เชียวชาญ จาก OCEAN LIFE ไทยสมุทรประกันชีวิต”.
Title: 63 characters
Your title is a healthy 63 characters: “OCEAN LIFE ไทยสมุทร | ประกันชีวิต ประกันสุขภาพ ประกันอุบัติเหตุ”.
Structured data in place
Structured data found: Organization and WebSite.
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.ocean.co.th/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.ocean.co.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.
2 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.
Other pages
3 pages share a title
/, https://www.ocean.co.th/th and https://www.ocean.co.th/en all use the title “OCEAN LIFE ไทยสมุทร | ประกันชีวิต ประกันสุขภาพ ประกันอุบัติเหตุ”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.ocean.co.th/service/sla-life-insurance has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.ocean.co.th/th and https://www.ocean.co.th/en use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://www.ocean.co.th/our-products, https://www.ocean.co.th/about-oceanlife and https://www.ocean.co.th/promotion have no <h1> headline, so visitors and search engines get no clear main topic.
10 pages with very little text
https://www.ocean.co.th/our-products, https://www.ocean.co.th/service, https://www.ocean.co.th/articles, https://www.ocean.co.th/ocean-club, https://www.ocean.co.th/group-insurance and https://www.ocean.co.th/contact and 4 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 51 found) and read each the way a search engine does.
4 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
36 of 44 tappable elements near the top are at least 24 px.
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.
Only about 131 words
The homepage has only about 131 words of visible text; thin pages give Google and first-time buyers little to go on.
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
3 short forms
3 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 3 phone links and 1 email link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 3 mores (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.
49 cookies set on arrival
49Opening the homepage sets 49 cookies, 1 of them by other companies (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.
35 other companies contacted
Loading the homepage contacts 35 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 ocean.co.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
- Bootstrap
- Analytics
- Google Tag Manager
- Hosting
- Uih Bbb As Ap Uih
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on ocean.co.th, including 20 speed issues, 2 SEO issues and 4 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.