Website review, no card needed

gfxco.com logo

gfxco.com website review

Visit site (opens in a new tab)Reviewed 22 October 202638 issues · 81 checks

This review found 38 issues worth fixing on gfxco.com, 15 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of gfxco.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gfxco.com at 0.5 s0.5 s
  2. gfxco.com at 1.1 s1.1 s
  3. gfxco.com at 1.6 s1.6 s
  4. gfxco.com at 2.1 s2.1 s
  5. gfxco.com at 2.6 s2.6 s
  6. gfxco.com at 3.2 s3.2 s
  7. gfxco.com at 3.7 s3.7 s
  8. gfxco.com at 4.2 s4.2 s

Speed

11 to fix28
  • Reduce unused JavaScript

    6.4 s · 3.8 MB

    About 3.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.4 s faster on a phone.

  • Render-blocking requests

    2.9 s

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

  • jotfor.ms adds 1.3 s

    1.3 s

    jotfor.ms costs a phone 1.3 s of main-thread work and 4.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 28

    28/100

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

  • Main-thread work: 6.6 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (jotfor.ms, jotform.com and Google Tag Manager and others), adding 7.2 MB and 2.5 s of main-thread time.

  • Use efficient cache lifetimes

    2.1 MB

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

  • 17 long tasks on the main thread

    17 long tasks block the main thread while loading, the longest for 1.3 s. During a long task the page ignores taps.

  • Reduce unused CSS

    900 ms · 346 KiB

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

  • jotform.com adds 929 ms

    929 ms

    jotform.com costs a phone 929 ms of main-thread work and 2.6 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.

  • Improve image delivery

    851 KiB

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

  • Legacy JavaScript

    100 ms · 19 KiB

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

  • Font display

    50 ms

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

  • Minify JavaScript

    37 KiB

    37 KiB could be saved by minifying JavaScript.

  • Phones get a much slower page than desktops

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

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

1 checks passed
  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix36
  • First Contentful Paint: 17.8 s

    17.8 s

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

  • Largest Contentful Paint: 23.0 s

    23.0 s

    Your largest element takes 23.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “how it works step one”.

  • Speed Index: 17.8 s

    17.8 s

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

  • Time to Interactive: 51.7 s

    51.7 s

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

  • Total Blocking Time: 1.8 s

    1.8 s

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

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

1 checks passed
  • Cumulative Layout Shift: 0.024

    0.024

    The layout barely moves while loading (CLS 0.024, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 10.3 MB in 173 requests

    10.3 MB

    Your homepage downloads 10.3 MB in 173 requests on a phone: scripts 6.3 MB (97), images 1.5 MB (26) and media 1.2 MB (2). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    2 KiB

    1 image is downloaded at several times the size a phone draws it, for example image at 715 px wide, shown at 234 px. Resized copies would save about 2 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (105 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.9 g of CO₂ per visit

    2.91 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

7 to fixGoogle 8490
  • Certain ARIA roles must be contained by particular parents (7 elements)

    Certain ARIA roles must be contained by particular parents: 7 elements on the page fail this check, rated critical by axe-core.

  • Certain ARIA roles must contain particular children (1 element)

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • All page content should be contained by landmarks (17 elements)

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

  • No main landmark

    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)

    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 form fields without a label

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

  • Headings skip levels

    Headings skip levels (h1 → h5, h3 → h6 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 28 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9279
  • Title is short (24 characters)

    Your title is only 24 characters: “gfx Product Personalizer”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 20 links crawlers can't follow

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

  • No XML sitemap

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

  • No robots.txt

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

  • 15 internal links, 6 external

    The homepage links to 15 pages on gfxco.com and 6 external pages.

4 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “Let your customers design unique products with flexible rules, real-time previews, and Printful integration. Plans star…”.

  • One H1 headline

    Your main headline reads: “Empower your Shopify store with gfx real-time customization.”.

  • Canonical URL set

    The canonical URL is https://gfxco.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

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

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (389 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix85
  • 6 pages point its canonical at the homepage

    https://gfxco.com/blog/best-blank-apparel-for-dtg-printing-2025, https://gfxco.com/blog/choosing-the-right-print-method-for-custom-apparel, https://gfxco.com/blog/getting-started-creating-a-design-with-gfx, https://gfxco.com/blog, https://gfxco.com/return-policy and https://gfxco.com/cookie-policy declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 1 page without an H1

    https://gfxco.com/return-policy has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://gfxco.com/return-policy has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 6 internal pages checked

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

5 checks passed
  • Linked pages load

    All 6 pages we checked loaded without an error.

  • Every page has a meta description

    All 6 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7388
  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    9 of 9 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • Thin social proof

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

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

  • About 385 words of copy

    The homepage carries about 385 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact us”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact us”, “Try this on my Shopify store” and “See demo store”.

  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies (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.

  • 7 other companies contacted

    Loading the homepage contacts 7 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 gfxco.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2024.

Stack

Framework
Next.js
Analytics
Google Analytics
Hosting
Vercel

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on gfxco.com, including 16 speed issues, 5 SEO issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25