Website review, no card needed
atomy.kr website review
Visit site (opens in a new tab)Reviewed 28 October 202644 issues · 87 checks
This review found 44 issues worth fixing on atomy.kr, 15 of them high impact, across 87 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.7 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 355 ms |
| May 16, 2026 | 357 ms |
| May 23, 2026 | 362 ms |
| May 30, 2026 | 361 ms |
| Jun 6, 2026 | 364 ms |
| Jun 13, 2026 | 362 ms |
| Jun 20, 2026 | 357 ms |
| Jun 27, 2026 | 358 ms |
| Jul 4, 2026 | 354 ms |
| Jul 11, 2026 | 354 ms |
| Jul 18, 2026 | 358 ms |
| Jul 25, 2026 | 357 ms |
| Aug 1, 2026 | 360 ms |
| Aug 8, 2026 | 358 ms |
| Aug 15, 2026 | 357 ms |
| Aug 22, 2026 | 361 ms |
| Aug 29, 2026 | 362 ms |
| Sep 5, 2026 | 365 ms |
| Sep 12, 2026 | 367 ms |
| Sep 19, 2026 | 365 ms |
| Sep 26, 2026 | 363 ms |
| Oct 3, 2026 | 360 ms |
| Oct 10, 2026 | 355 ms |
| Oct 17, 2026 | 354 ms |
| Oct 24, 2026 | 354 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
Speed
Use efficient cache lifetimes
3.3 s · 4.2 MB141 files are served with short cache lifetimes, so returning visitors download them again (4.2 MB).
Render-blocking requests
4.0 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.0 s.
Improve image delivery
1.6 s · 2.2 MB19 images could be 2.2 MB 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.
Document request latency
1.5 sThe HTML itself could arrive about 1.5 s sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce unused JavaScript
1.1 s · 226 KiBAbout 226 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 52
52/100Your mobile performance score is 52 (desktop: 85). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 190 KiBAbout 190 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Avoid multiple page redirects
780 msThe page goes through 1 redirect before it starts loading, costing about 780 ms. Link and advertise the final URL directly.
Reduce initial server response time
676 msReduce initial server response time. Google estimates savings of 676 ms on a phone.
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 286 ms
286 msGoogle Tag Manager costs a phone 286 ms of main-thread work and 291 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.
Server response: 776 ms
776 msYour server takes 776 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Google Fonts adds 0 ms
0 msGoogle Fonts costs a phone 0 ms of main-thread work and 436 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.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, datadoghq-browser-agent.com and Google Fonts and others), adding 787 KiB and 412 ms of main-thread time.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 126 ms. During a long task the page ignores taps.
Minify JavaScript
40 ms · 33 KiB33 KiB could be saved by minifying JavaScript.
Minify CSS
17 KiB17 KiB could be saved by minifying CSS.
Phones get a much slower page than desktops
Desktop scores 85 but mobile only 52. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
Core Web Vitals
Largest Contentful Paint: 14.7 s
14.7 sYour largest element takes 14.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “대한민국 배드민턴 국가대표 메달획득 기념 프로모션”.
First Contentful Paint: 5.9 s
5.9 sThe first text or image appears after 5.9 s on a phone. Good is under 1.8 s.
Speed Index: 11.5 s
11.5 sVisually, the page fills in at 11.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 14.9 s
14.9 sThe page becomes fully interactive after 14.9 s. Good is under 3.8 s.
17 images without width and height
17 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 220 ms
220 msScripts block taps and scrolling for 220 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 355 ms to 354 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 93 ms
93 msReal visitors wait 93 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.
Real-user TTFB: 642 ms
642 msReal visitors wait 642 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.015
0.015The layout barely moves while loading (CLS 0.015, good is under 0.1).
Images and page weight
Page weight: 5.0 MB in 171 requests
5.0 MBYour homepage downloads 5.0 MB in 171 requests on a phone: images 3.9 MB (90), scripts 603 KiB (50) and fonts 275 KiB (14). Under 2 MB keeps phones on slow connections fast.
About 1.4 g of CO₂ per visit
1.41 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.41 g of CO₂e: 168.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
[role]s are not contained by their required parent element
[role]s are not contained by their required parent element (4 elements).
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
Orphan list items
Some list items are not inside a list.
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.
ARIA input fields do not have accessible names
ARIA input fields do not have accessible names (2 elements).
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 73 images in the HTML carry an alt attribute.
4 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 7 WCAG 2.2 A/AA and best-practice rules on the phone render: 4 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (15 characters)
Your title is only 15 characters: “쇼핑몰 | 애터미 ATOMY”. Between 30 and 65 characters leaves room to say what you do and for whom.
39 links crawlers can't follow
39 links have no real href, so search engines can't follow them.
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.
No XML sitemap
No XML sitemap at https://kr.atomy.com/sitemap.xml, so Google discovers your pages only by following links.
One H1 headline
Your <h1> is empty.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
55 internal links, 11 external
The homepage links to 55 pages on atomy.kr and 11 external pages.
3 checks passed
Meta description: 83 characters
Your meta description is 83 characters: “충청남도 공주시 웅진동에 위치, 화장품 및 건강기능식품 전문업체, 한방헤어, 바디케어, 치약, 헤모힘, 앱솔루트, 아델리카, 슬림바디 등 제품 안내.”.
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.
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://kr.atomy.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
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Other pages
6 pages slow to respond
https://kr.atomy.com/product/030101, https://kr.atomy.com/product/000017, https://kr.atomy.com/product/000014, https://kr.atomy.com/product/005190, https://kr.atomy.com/product/000227 and https://kr.atomy.com/product/000247 took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 29 found) and read each the way a search engine does.
7 checks passed
Linked pages load
7 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 7 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 7 pages that loaded have a <title>.
Best practices
No mobile viewport
No viewport meta tag, so phones render the desktop layout zoomed out.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 218 words
The homepage has only about 218 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 Tag Manager and Google Analytics.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
4 other companies contacted
Loading the homepage contacts 4 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 atomy.kr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2023.
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- AWS
Company
- Founded
- 2009
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on atomy.kr, including 19 speed issues, 6 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.