twoscompany.com website review

86 files are served with short cache lifetimes, so returning visitors download them again (109.8 MB).

11 images could be 25.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 25.6 s faster on a phone.

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

Your mobile performance score is 5 (desktop: 34). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 2.2 MB and 1.9 s of main-thread time.

About 2.0 MB of JavaScript is downloaded but never used on this page.

About 161 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.

Google CDN costs a phone 752 ms of main-thread work and 765 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 block the main thread while loading, the longest for 651 ms. During a long task the page ignores taps.

Google Tag Manager costs a phone 501 ms of main-thread work and 517 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 Maps costs a phone 205 ms of main-thread work and 392 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.

56 KiB could be saved by minifying JavaScript.

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

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

Desktop scores 34 but mobile only 5. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

The layout shifts by 1.029 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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.

Your homepage downloads 112.2 MB in 154 requests on a phone: images 107.0 MB (39), scripts 4.3 MB (77) and other files 366 KiB (15). Under 2 MB keeps phones on slow connections fast.

29 images weigh 105.1 MB together. On a phone connection a single image that size takes seconds.

11 images are downloaded at several times the size a phone draws them, for example shop-catalog.jpg at 9,375 px wide, shown at 371 px. Resized copies would save about 24.1 MB.

34 images (107.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.

7 images further down the page (6.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

18 visible links have no text or label, so screen readers cannot say where they go.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

Your title is 81 characters, so Google will cut it off around 60: “Two's Company | Wholesale Home Décor, Women's Fashion, Kids Gifts & so much more!”.

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

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://twoscompany.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at twoscompany.com/robots.txt, the first file search crawlers ask for.

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

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

The homepage links to 327 pages on twoscompany.com and 8 external pages.

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.

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

Your homepage links to https://twoscompany.com/asdsa, https://twoscompany.com/asda and https://twoscompany.com/asdfa, which answer with an error. Visitors hit a dead end and search engines drop them.

https://twoscompany.com/shop, https://twoscompany.com/collections/al-fresco, https://twoscompany.com/brands/eat-art, https://twoscompany.com/collections/pretty-please, https://twoscompany.com/collections/red-white-and-blue and https://twoscompany.com/holidays/bunny-trail and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://twoscompany.com/holidays/bunny-trail, whose canonical is https://twoscompany.com/holidays/bunnies-plus-bows. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://twoscompany.com/shop and https://twoscompany.com/brands/eat-art have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://www.pages09.net/WTS/event.jpeg?accesskey=23eac84f-180d7613f17-1419df2995b6650da6b069c5b56a0daa&v=1.31&isNewSession=1&type=pageview&isNewVisitor=1&sessionGUID=d6ac021e-b6ed-e03c-e5ac-7e11e8b962.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Large scripts ship without source maps.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 13 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

Opening the homepage sets 13 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.