Website review, no card needed
oasis7.co.kr website review
Visit site (opens in a new tab)Reviewed 17 November 202642 issues · 77 checks
This review found 42 issues worth fixing on oasis7.co.kr, 16 of them high impact, across 77 checks. The most urgent: reduce unused JavaScript. 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
66D- #107,815 of 117,883 reviewed websitesbeats 7%
- #64,095 of 67,013 online storesbeats 4%
- #1,335 of 1,422 Squarespace websitesbeats 4%
Closest competitors among online stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Aug 1, 2026 | 79 ms |
| Aug 8, 2026 | 78 ms |
| Aug 22, 2026 | 78 ms |
| Aug 29, 2026 | 71 ms |
| Sep 5, 2026 | 71 ms |
| Sep 12, 2026 | 70 ms |
| Sep 19, 2026 | 72 ms |
| Sep 26, 2026 | 76 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.4 s
0.9 s
1.3 s
1.8 s
2.2 s
2.6 s
3.1 s
3.5 s
Speed
Reduce unused JavaScript
7.2 s · 1,016 KiBAbout 1,016 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.2 s faster on a phone.
Improve image delivery
3.5 s · 3.8 MB16 images could be 3.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.5 s faster on a phone.
Render-blocking requests
4.2 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.2 s.
Mobile performance score: 44
44/100Your mobile performance score is 44. 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 (Squarespace, Google CDN and Other Google APIs/SDKs and others), adding 12.3 MB and 920 ms of main-thread time.
Reduce unused CSS
900 ms · 230 KiBAbout 230 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
squarespace-cdn.com adds 0 ms
0 mssquarespace-cdn.com costs a phone 0 ms of main-thread work and 9.7 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.
Squarespace adds 587 ms
587 msSquarespace costs a phone 587 ms of main-thread work and 1.4 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.
Google CDN adds 276 ms
276 msGoogle CDN costs a phone 276 ms of main-thread work and 773 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.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
200 ms · 110 KiBPolyfills for old browsers add 110 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 182 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
100 ms · 27 KiB4 files are served with short cache lifetimes, so returning visitors download them again (27 KiB).
Minify JavaScript
17 KiB17 KiB could be saved by minifying JavaScript.
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: 54 ms
54 msYour server sent the HTML in 54 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 12.1 s
12.1 sThe first text or image appears after 12.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 24.0 s
24.0 sYour largest element takes 24.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 24.2 s
24.2 sThe page becomes fully interactive after 24.2 s. Good is under 3.8 s.
Speed Index: 12.1 s
12.1 sVisually, the page fills in at 12.1 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) got 29% slower for real visitors
+29%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.6 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.145
0.145The layout shifts by 0.145 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 275 ms
275 msScripts block taps and scrolling for 275 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image 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-11-14, real Chrome visitors' tap response (inp) went from 79 ms to 76 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
Images and page weight
Page weight: 12.9 MB in 120 requests
12.9 MBYour homepage downloads 12.9 MB in 120 requests on a phone: images 9.7 MB (22), scripts 2.0 MB (61) and other files 504 KiB (7). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
pop+up+3.7+.png weighs 5.2 MB. On a phone connection a single image that size takes seconds.
An image on the first screen is lazy-loaded
Leaf+Background.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image far larger than shown
60 KiB1 image is downloaded at several times the size a phone draws it, for example Feet+for+Blog.jpg at 2,500 px wide, shown at 343 px. Resized copies would save about 60 KiB.
3 images below the first screen load straight away
3 images further down the page (297 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.6 g of CO₂ per visit
3.64 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.64 g of CO₂e: 437.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
3 text elements with low contrast
3 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.
3 links without text
3 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.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (7 characters)
Your title is only 7 characters: “Oasis 7”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 1 problem
Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/5fe5b7659e3b641caab…”.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
66 internal links, 22 external
The homepage links to 66 pages on oasis7.co.kr and 22 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.oasis7.co.kr/.
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.oasis7.co.kr/sitemap.xml.
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://www.oasis7.co.kr/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.
Text is in the HTML
Your server sends the page's text in the HTML (452 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.oasis7.co.kr/our-products and https://www.oasis7.co.kr/new-folder all use the title “Our Products — Oasis 7”. Search engines can't tell which page to show for a search, so each competes with the others.
12 pages without a meta description
https://www.oasis7.co.kr/our-products, https://www.oasis7.co.kr/our-products/for-your-face/ampoule, https://www.oasis7.co.kr/our-products/for-your-face/eye-cream, https://www.oasis7.co.kr/our-products/for-your-face/serum, https://www.oasis7.co.kr/our-products/for-your-face/mask and https://www.oasis7.co.kr/our-products/footcare/foot-moisturizing and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
8 links to non-canonical URLs
Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://www.oasis7.co.kr/our-products/for-your-face/ampoule, whose canonical is https://www.oasis7.co.kr/our-products. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
12 pages without an H1
https://www.oasis7.co.kr/our-products, https://www.oasis7.co.kr/our-products/for-your-face/ampoule, https://www.oasis7.co.kr/our-products/for-your-face/eye-cream, https://www.oasis7.co.kr/our-products/for-your-face/serum, https://www.oasis7.co.kr/our-products/for-your-face/mask and https://www.oasis7.co.kr/our-products/footcare/foot-moisturizing and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 24 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.
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
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Subresource Integrity: The resource 'https://use.fontawesome.com/releases/v5.12.0/css/all.css' has an integrity attribu…”.
2 checks passed
Tap targets are thumb-sized
17 of 17 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
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.
About 321 words of copy
The homepage carries about 321 words of visible text.
2 checks passed
5 calls to action
The homepage has 5 calls to action, for example “SHOP”, “LEARN MORE” and “CONTACT”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
13 other companies contacted
Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 oasis7.co.kr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Squarespace
- Framework
- jQuery
- Hosting
- Squarespace
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on oasis7.co.kr, including 18 speed issues, 5 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.