copyworks.com website review

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

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

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

6 third-party services load with your homepage (firespring.com, Google Tag Manager and sitesearch360.com and others), adding 1.3 MB and 482 ms of main-thread time.

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

firespring.com costs a phone 224 ms of main-thread work and 912 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.

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

2 images could be 22 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Polyfills for old browsers add 20 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

Your largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We can help to design your next project. Just ask for our d…”.

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

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

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

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

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

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

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

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

Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

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

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

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

Your title is only 19 characters: “Welcome : Copyworks”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 116 pages on copyworks.com and 5 external pages.

https://www.copyworks.com/products and https://www.copyworks.com/products/products all use the title “Business Cards : Products : Products & Services : Copyworks”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.copyworks.com/products and https://www.copyworks.com/products/products use the same meta description. A description written for each page earns more clicks.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.copyworks.com/products, whose canonical is https://www.copyworks.com/products/products/business-cards.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.firespring.com/designs/pp_luminous/css/design-3916.1794381188.css' from origin…”.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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 311 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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 10 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.