Website review, no card needed

ym-inc.com logo

ym-inc.com website review

Visit site (opens in a new tab)Reviewed 30 October 202632 issues · 84 checks

This review found 32 issues worth fixing on ym-inc.com, 8 of them high impact, across 84 checks. The most urgent: render-blocking 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
978 ms855 msMay 9Oct 24933 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026869 ms
May 16, 2026879 ms
May 23, 2026879 ms
May 30, 2026898 ms
Jun 6, 2026870 ms
Jun 13, 2026874 ms
Jun 20, 2026905 ms
Jun 27, 2026931 ms
Jul 4, 2026950 ms
Jul 11, 2026962 ms
Jul 18, 2026944 ms
Jul 25, 2026922 ms
Aug 1, 2026922 ms
Aug 8, 2026926 ms
Aug 15, 2026949 ms
Aug 22, 2026954 ms
Aug 29, 2026961 ms
Sep 5, 2026940 ms
Sep 12, 2026917 ms
Sep 19, 2026942 ms
Sep 26, 2026934 ms
Oct 3, 2026949 ms
Oct 10, 2026964 ms
Oct 17, 2026933 ms
Oct 24, 2026933 ms
Real-visitor tap response (INP)75th percentile, phones
71 ms62 msMay 9Oct 2467 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202664 ms
May 16, 202663 ms
May 23, 202663 ms
May 30, 202664 ms
Jun 6, 202664 ms
Jun 13, 202666 ms
Jun 20, 202668 ms
Jun 27, 202669 ms
Jul 4, 202669 ms
Jul 11, 202670 ms
Jul 18, 202669 ms
Jul 25, 202669 ms
Aug 1, 202667 ms
Aug 8, 202665 ms
Aug 15, 202665 ms
Aug 22, 202664 ms
Aug 29, 202666 ms
Sep 5, 202666 ms
Sep 12, 202664 ms
Sep 19, 202664 ms
Sep 26, 202663 ms
Oct 3, 202664 ms
Oct 10, 202668 ms
Oct 17, 202666 ms
Oct 24, 202667 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 ym-inc.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ym-inc.com at 0.4 s0.4 s
  2. ym-inc.com at 0.8 s0.8 s
  3. ym-inc.com at 1.1 s1.1 s
  4. ym-inc.com at 1.5 s1.5 s
  5. ym-inc.com at 1.9 s1.9 s
  6. ym-inc.com at 2.3 s2.3 s
  7. ym-inc.com at 2.6 s2.6 s
  8. ym-inc.com at 3.0 s3.0 s

Speed

4 to fix74
  • Render-blocking requests

    2.3 s

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

  • Mobile performance score: 74

    74/100

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

  • Reduce unused JavaScript

    450 ms · 103 KiB

    About 103 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Improve image delivery

    402 KiB

    21 images could be 402 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    290 ms · 62 KiB

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

  • Minify CSS

    150 ms · 8 KiB

    8 KiB could be saved by minifying CSS.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 135 ms. During a long task the page ignores taps.

  • Font display

    50 ms

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (FontAwesome CDN, Google Fonts and Google Analytics), adding 150 KiB and 10 ms of main-thread time.

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

  • Use efficient cache lifetimes

    4 KiB

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

2 checks passed
  • Main-thread work: 0.5 s

    A phone's processor spends 0.5 s on main-thread work while loading, 182 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix100
  • 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: 4.7 s

    4.7 s

    Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is element render delay (2.1 s).

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Speed Index: 4.9 s

    4.9 s

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

  • Time to Interactive: 4.7 s

    4.7 s

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

  • 5 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +5%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

5 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 77 ms

    77 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Total Blocking Time: 85 ms

    85 ms

    Scripts block the page for only 85 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 4.5 MB in 56 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 56 requests on a phone: media 3.5 MB (3), images 503 KiB (35) and scripts 240 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (150 KiB) 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 1.3 g of CO₂ per visit

    1.27 g

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

2 checks passed
  • Images load when needed

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8590
  • 7 buttons without a name

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

  • 4 text elements with low contrast

    4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

  • Alternative text of images should not be repeated as text (16 elements)

    Alternative text of images should not be repeated as text: 16 elements on the page fail this check, rated minor by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 39 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10086
  • Title is short (21 characters)

    Your title is only 21 characters: “YM Inc. Fashion House”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 1 problem

    Structured data found ((untyped), BreadcrumbList, WebPage and WebSite) but with 1 problem, for example “block has no @type”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 109 internal links, 9 external

    The homepage links to 109 pages on ym-inc.com and 9 external pages.

5 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “As one of North America’s largest fashion houses, YM Inc. is dedicated to delivering leading-edge fashion apparel to su…”.

  • One H1 headline

    Your main headline reads: “YM Inc.”.

  • Canonical URL set

    The canonical URL is https://ym-inc.com/.

  • 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://ym-inc.com/sitemap_index.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.

  • No llms.txt

    There is no https://ym-inc.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.

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

Other pages

3 to fix86
  • 2 pages share a title

    / and https://ym-inc.com/fr all use the title “YM Inc. Fashion House”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://ym-inc.com/about, https://ym-inc.com/philosophy, https://ym-inc.com/contact-us, https://ym-inc.com/brand/charlotte-russe and https://ym-inc.com/brand/aeropostale have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    https://ym-inc.com/brand and https://ym-inc.com/brand/urban-planet use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

5 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 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

2 to fixGoogle 9287
  • 17 small tap targets

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

  • 2 JavaScript errors while loading

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

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

  • About 596 words of copy

    The homepage carries about 596 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact Us”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Analytics (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

    2

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

  • 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 ym-inc.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Liquid Web

Company

Headquarters
Toronto

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on ym-inc.com, including 12 speed issues, 3 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