Website review, no card needed

atmos.co.id logo

atmos.co.id website review

Visit site (opens in a new tab)Reviewed 7 November 202654 issues · 99 checks

This review found 54 issues worth fixing on atmos.co.id, 18 of them high impact, across 99 checks. The most urgent: page weight: 20.5 MB in 249 requests. 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
1.6 s1.4 sMay 16Oct 311.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.4 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Oct 24, 20261.5 s
Oct 31, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
157 ms134 msMay 16Oct 31153 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026151 ms
May 23, 2026149 ms
May 30, 2026148 ms
Jun 6, 2026149 ms
Jun 13, 2026152 ms
Jun 20, 2026153 ms
Jun 27, 2026154 ms
Jul 4, 2026154 ms
Jul 11, 2026152 ms
Jul 18, 2026149 ms
Jul 25, 2026144 ms
Aug 1, 2026138 ms
Aug 8, 2026137 ms
Aug 15, 2026138 ms
Aug 22, 2026139 ms
Aug 29, 2026140 ms
Sep 5, 2026141 ms
Sep 12, 2026144 ms
Sep 19, 2026148 ms
Sep 26, 2026149 ms
Oct 3, 2026147 ms
Oct 10, 2026148 ms
Oct 17, 2026147 ms
Oct 24, 2026149 ms
Oct 31, 2026153 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 atmos.co.id (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. atmos.co.id at 1.0 s1.0 s
  2. atmos.co.id at 1.9 s1.9 s
  3. atmos.co.id at 2.9 s2.9 s
  4. atmos.co.id at 3.8 s3.8 s
  5. atmos.co.id at 4.8 s4.8 s
  6. atmos.co.id at 5.7 s5.7 s
  7. atmos.co.id at 6.7 s6.7 s
  8. atmos.co.id at 7.7 s7.7 s

Speed

15 to fix52
  • Render-blocking requests

    1.9 s

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

  • Main-thread work: 4.6 s

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

  • 3,482 HTML elements

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

  • Reduce unused JavaScript

    900 ms · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Improve image delivery

    1.9 MB

    63 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (jQuery CDN, Google Tag Manager and Shopify and others), adding 2.0 MB and 1.0 s of main-thread time.

  • Mobile performance score: 52

    52/100

    Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.

  • Minify JavaScript

    600 ms · 352 KiB

    352 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    300 ms · 383 KiB

    13 files are served with short cache lifetimes, so returning visitors download them again (383 KiB).

  • Reduce unused CSS

    450 ms · 80 KiB

    About 80 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • jQuery CDN adds 272 ms

    272 ms

    jQuery CDN costs a phone 272 ms of main-thread work and 290 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.

  • Google Tag Manager adds 223 ms

    223 ms

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

  • Shopify adds 199 ms

    199 ms

    Shopify costs a phone 199 ms of main-thread work and 368 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.

  • Google CDN adds 128 ms

    128 ms

    Google CDN costs a phone 128 ms of main-thread work and 382 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.

  • Cloudflare CDN adds 61 ms

    61 ms

    Cloudflare CDN costs a phone 61 ms of main-thread work and 335 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.

  • 20 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Legacy JavaScript

    35 KiB

    Polyfills for old browsers add 35 KiB JavaScript that modern phones do not need.

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 22 ms

    22 ms

    Your server sent the HTML in 22 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.

  • Largest Contentful Paint: 18.3 s

    18.3 s

    Your largest element takes 18.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 33.0 s

    33.0 s

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

  • Speed Index: 7.0 s

    7.0 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user INP: 207 ms

    207 ms

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

  • Total Blocking Time: 568 ms

    568 ms

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

  • 30 images without width and height

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

4 checks passed
  • Real-user CLS: 0.03

    0.03

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 489 ms

    489 ms

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

  • Cumulative Layout Shift: 0.034

    0.034

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

Images and page weight

4 to fix25
  • Page weight: 20.5 MB in 249 requests

    20.5 MB

    Your homepage downloads 20.5 MB in 249 requests on a phone: media 12.2 MB (2), images 4.8 MB (99) and scripts 2.1 MB (60). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    ATMOS6730.jpg weighs 785 KiB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    676 KiB

    2 images are downloaded at several times the size a phone draws them, for example BANNER_ATMOS_1500x1500_ed3e5986-551b-45d9-8e26-1df627569f19. at 1,500 px wide, shown at 195 px. Resized copies would save about 676 KiB.

  • 6 images in older formats

    6 images (1.1 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.

  • About 5.8 g of CO₂ per visit

    5.81 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

12 to fixGoogle 7385
  • 4 buttons without a name

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

  • ARIA attributes must conform to valid names (2 elements)

    ARIA attributes must conform to valid names: 2 elements on the page fail this check, rated critical by axe-core.

  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 13 images without alt text

    13 images have no alt text, which hurts accessibility and image search.

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

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

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

    Document should not have more than one banner 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.

  • 11 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h4 → h6, h4 → h6 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 43 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: 43 passed and 11 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8572
  • No H1 headline

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

  • Title is short (15 characters)

    Your title is only 15 characters: “atmos Indonesia”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is short (26 characters)

    Your meta description is only 26 characters: “Atmos was founded in Tokyo”. 70 to 160 characters is enough to sell the click.

  • 2 links crawlers can't follow

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

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 450 internal links, 15 external

    The homepage links to 450 pages on atmos.co.id and 15 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://atmos.co.id/.

  • 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://atmos.co.id/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

3 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 (1,434 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://atmos.co.id/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 6 pages share 3 titles

    https://atmos.co.id/products/adidas-adizero-evo-sl-m-ftwr-white-lc3794 and https://atmos.co.id/products/adidas-adizero-evo-sl-m-core-black-lc3795 all use the title “ADIDAS ADIZERO EVO SL M”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages share a meta description

    https://atmos.co.id/products/adidas-adizero-evo-sl-m-ftwr-white-lc3794 and https://atmos.co.id/products/adidas-adizero-evo-sl-m-core-black-lc3795 use the same meta description. A description written for each page earns more clicks.

  • 8 pages slow to respond

    https://atmos.co.id/collections/new-arrivals, https://atmos.co.id/collections/apparel, https://atmos.co.id/collections/accessories-1, https://atmos.co.id/products/adidas-adistar-control-5-atmos-earth-strata-kz6953, https://atmos.co.id/products/adidas-adizero-evo-sl-m-ftwr-white-lc3794 and https://atmos.co.id/products/adidas-adizero-evo-sl-m-core-black-lc3795 and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 2 broken images

    2 images failed to load on a phone, for example https://atmos.co.id/.

  • 86 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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.

  • Thin social proof

    Social proof on the homepage: 9 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 1,074 words of copy

    The homepage carries about 1,074 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • 12 calls to action

    The homepage has 12 calls to action, for example “Shop By”, “Track your order” and “Contact Us”.

  • 3 short forms

    3 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 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.

  • 37 other companies contacted

    Loading the homepage contacts 37 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 atmos.co.id, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Social Chat Live Chat · devbdd.com · webmarked.net · nfcube.com · amazonaws.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 54 issues on atmos.co.id, including 24 speed issues, 5 SEO issues and 2 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