kaastailored.com website review

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

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

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

About 325 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and FullStory and others), adding 1.8 MB and 458 ms of main-thread time.

WP Engine costs a phone 0 ms of main-thread work and 1.2 MB 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.

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

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

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

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

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 15.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Shine Our Light We believe in doing high quality work with …”.

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

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

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

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

JC_6319-2.jpg weighs 961 KiB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example JC_6319-2.jpg at 1,600 px wide, shown at 348 px. Resized copies would save about 732 KiB.

Your homepage downloads 2.4 MB in 48 requests on a phone: images 1.7 MB (5), scripts 576 KiB (17) and stylesheets 75 KiB (11). Under 2 MB keeps phones on slow connections fast.

2 images (1.2 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.

2 images further down the page (1.2 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 0.68 g of CO₂e: 81.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 7 elements on the page fail this check, rated minor by axe-core.

Your title is 67 characters, so Google will cut it off around 60: “Manufacturing Solutions for the Upholstery Industry | Kaas Tailored”.

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

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 29 pages on kaastailored.com and 16 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://kaastailored.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://kaastailored.com/about-us/design-os, which answers with an error. Visitors hit a dead end and search engines drop it.

https://kaastailored.com/careers and https://kaastailored.com/contact/careers all use the title “Careers: Manufacturing Jobs in Mukilteo | Kaas Tailored”. Search engines can't tell which page to show for a search, so each competes with the others.

https://kaastailored.com/contact, https://kaastailored.com/blog, https://kaastailored.com/ponotes, https://kaastailored.com/terms-and-conditions, https://kaastailored.com/privacy-policy and https://kaastailored.com/tax-information have no meta description, so Google writes the search snippet from whatever text it finds.

https://kaastailored.com/careers and https://kaastailored.com/contact/careers use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://kaastailored.com/contact/careers, whose canonical is https://kaastailored.com/careers. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://kaastailored.com/about-us, https://kaastailored.com/contact, https://kaastailored.com/ponotes, https://kaastailored.com/terms-and-conditions, https://kaastailored.com/privacy-policy and https://kaastailored.com/tax-information and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 13 pages linked from your homepage and read each the way a search engine does.

2 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 ()”.

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

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

The homepage carries about 337 words of visible text.

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

Opening the homepage sets 15 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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.