Website review, no card needed
iabmfg.com website review
Visit site (opens in a new tab)Reviewed 16 November 202633 issues · 77 checks
This review found 33 issues worth fixing on iabmfg.com, 10 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
70C- #96,016 of 114,551 reviewed websitesbeats 14%
- #59,597 of 66,237 online storesbeats 8%
- #55,412 of 60,613 Shopify storesbeats 7%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jun 20, 2026 | 948 ms |
| Jun 27, 2026 | 941 ms |
| Jul 4, 2026 | 895 ms |
| Jul 11, 2026 | 865 ms |
| Jul 18, 2026 | 887 ms |
| Jul 25, 2026 | 845 ms |
| Aug 8, 2026 | 936 ms |
| Aug 15, 2026 | 933 ms |
| Aug 29, 2026 | 930 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jun 27, 2026 | 63 ms |
| Jul 4, 2026 | 63 ms |
| Jul 11, 2026 | 62 ms |
| Jul 25, 2026 | 65 ms |
| Aug 8, 2026 | 68 ms |
| Aug 15, 2026 | 70 ms |
| Aug 29, 2026 | 71 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.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
1.4 s · 540 KiBAbout 540 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Render-blocking requests
1.0 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Mobile performance score: 57
57/100Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, rechargecdn.com and Hotjar and others), adding 1,019 KiB and 842 ms of main-thread time.
Google Tag Manager adds 343 ms
343 msGoogle Tag Manager costs a phone 343 ms of main-thread work and 381 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.
Reduce unused CSS
300 ms · 41 KiBAbout 41 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 278 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
219 KiB16 files are served with short cache lifetimes, so returning visitors download them again (219 KiB).
Legacy JavaScript
150 ms · 64 KiBPolyfills for old browsers add 64 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
150 ms · 14 KiB14 KiB could be saved by minifying JavaScript.
Improve image delivery
55 KiB2 images could be 55 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.0 s
9.0 sYour largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 15.3 s
15.3 sThe page becomes fully interactive after 15.3 s. Good is under 3.8 s.
Total Blocking Time: 599 ms
599 msScripts block taps and scrolling for 599 ms in total while the page loads. Good is under 200 ms.
Speed Index: 4.3 s
4.3 sVisually, the page fills in at 4.3 s (Speed Index). Good is under 3.4 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) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 63 ms to 71 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-11-14, 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).
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.
2 checks passed
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.7 MB in 203 requests
2.7 MBYour homepage downloads 2.7 MB in 203 requests on a phone: scripts 1.3 MB (71), other files 765 KiB (107) and images 325 KiB (10). Under 2 MB keeps phones on slow connections fast.
About 0.8 g of CO₂ per visit
0.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.77 g of CO₂e: 92.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Orphan list items
Some list items are not inside a list.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (72 characters)
Your title is 72 characters, so Google will cut it off around 60: “I AM BECOMING - Athletic Apparel for the Modern Athlete – I A B | M F G.”.
2 H1 headlines
There are 2 <h1> headlines (“<img src="//www.iambecoming.com/cdn/shop/files/ia…” and “Notify me when available”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
73 internal links, 10 external
The homepage links to 73 pages on iabmfg.com and 10 external pages.
5 checks passed
Meta description: 125 characters
Your meta description is 125 characters: “I AM BECOMING - Always evolving to become the best version of ourselves. More than just a clothing company, it's a life…”.
Canonical URL set
The canonical URL is https://www.iambecoming.com/.
Structured data in place
Structured data found: Organization and WebSite.
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.iambecoming.com/sitemap.xml.
AI search readiness
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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
llms.txt published
The site publishes https://www.iambecoming.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
12 pages without a meta description
https://www.iambecoming.com/collections/new-arrivals, https://www.iambecoming.com/collections/3-inch-no-ride, https://www.iambecoming.com/collections/5-inch-no-ride-1, https://www.iambecoming.com/collections/all-shorts, https://www.iambecoming.com/collections/no-ride-pockets and https://www.iambecoming.com/collections/pocket-5-inch-fit-grip and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 33 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.
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 15 pages that loaded have a <title>.
Best practices
14 small tap targets
14 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “MinMaxify is deactivated for this website. Please don't forget to remove minmaxify-head.liquid still being referenced b…”.
1 checks passed
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.
Only about 84 words
The homepage has only about 84 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.
4 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Subscribe”, “CONTACT US” and “Shop Now”.
5 short forms
5 short forms (3 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Hotjar and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 2 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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
29 other companies contacted
Loading the homepage contacts 29 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 iabmfg.com, 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 4 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
cartsguru.io · rechargecdn.com · cloudfront.net · klaviyo.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 Analytics | Google Tag Manager | Hotjar
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on iabmfg.com, including 13 speed issues, 4 SEO issues and 3 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.