4by6.com website review

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

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

5 third-party services load with your homepage (hcaptcha.com, Shopify and uploadly-cdn.com and others), adding 2.3 MB and 1.4 s of main-thread time.

hcaptcha.com costs a phone 966 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.

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

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

Shopify costs a phone 231 ms of main-thread work and 1.0 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.

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

The page has 1,625 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Polyfills for old browsers add 59 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

About 11 KiB of CSS is downloaded but never applied on this page.

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.

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

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

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

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

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

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 4.4 MB in 377 requests on a phone: scripts 1.8 MB (168), images 1.0 MB (23) and other files 913 KiB (149). Under 2 MB keeps phones on slow connections fast.

Student-promo-Hero-O1_685e2c2b-e7ba-4168-bb8a-e5f70cc6ac7a.j is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

7 images are downloaded at several times the size a phone draws them, for example Student-promo-Hero-O1_685e2c2b-e7ba-4168-bb8a-e5f70cc6ac7a.j at 2,000 px wide, shown at 390 px. Resized copies would save about 400 KiB.

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

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

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Your title is only 18 characters: “The 4by6.com Store”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is 231 characters; Google truncates after about 160, so the end of your pitch is cut.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Your <h1> is empty.

The homepage links to 57 pages on 4by6.com and 1 external page.

/products/rounded-satin-business-cards, /products/raised-foil-business-cards-copy and /products/embossed-gloss-business-cards all use the title “Custom Business Cards - Professional Printing – 4by6.com Store”. Search engines can't tell which page to show for a search, so each competes with the others.

/pages/design-studio has no meta description, so Google writes the search snippet from whatever text it finds.

/products/rounded-satin-business-cards, /products/raised-foil-business-cards-copy and /products/embossed-gloss-business-cards use the same meta description. A description written for each page earns more clicks.

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

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

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://4by6.com/customer_authentication/redirect?locale=en&region_country=US.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

4by6.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

4by6.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

DMARC is set to p=none, so mail pretending to be 4by6.com is still delivered. Reports are on, so moving to quarantine is the next step.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Opening the homepage sets 8 cookies, 1 of them by other companies (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.