Website review, no card needed

impressionsprinting.com logo

impressionsprinting.com website review

Visit site (opens in a new tab)Reviewed 22 October 202634 issues · 85 checks

This review found 34 issues worth fixing on impressionsprinting.com, 15 of them high impact, across 85 checks. The most urgent: render-blocking requests. 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

Real-visitor load time (LCP)75th percentile, phones
5.1 s3.0 sMay 2Oct 104.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.7 s
May 9, 20264.3 s
May 16, 20264.3 s
May 23, 20264.8 s
May 30, 20264.1 s
Jun 6, 20263.9 s
Jun 13, 20264.0 s
Jun 20, 20263.8 s
Jun 27, 20263.8 s
Jul 4, 20263.5 s
Jul 11, 20263.3 s
Jul 18, 20263.5 s
Jul 25, 20263.4 s
Aug 1, 20263.5 s
Aug 8, 20263.5 s
Aug 15, 20263.2 s
Aug 22, 20263.4 s
Aug 29, 20263.6 s
Sep 5, 20263.9 s
Sep 12, 20263.7 s
Sep 19, 20263.7 s
Sep 26, 20263.6 s
Oct 3, 20263.6 s
Oct 10, 20264.0 s

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

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

How it loaded on a phone

  1. impressionsprinting.com at 0.5 s0.5 s
  2. impressionsprinting.com at 1.0 s1.0 s
  3. impressionsprinting.com at 1.6 s1.6 s
  4. impressionsprinting.com at 2.1 s2.1 s
  5. impressionsprinting.com at 2.6 s2.6 s
  6. impressionsprinting.com at 3.1 s3.1 s
  7. impressionsprinting.com at 3.7 s3.7 s
  8. impressionsprinting.com at 4.2 s4.2 s

Speed

10 to fix40
  • Render-blocking requests

    2.3 s

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

  • Google Tag Manager adds 1.1 s

    1.1 s

    Google Tag Manager costs a phone 1.1 s of main-thread work and 1.3 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: 40

    40/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, firespring.com and Facebook and others), adding 4.7 MB and 1.7 s of main-thread time.

  • Reduce unused JavaScript

    750 ms · 879 KiB

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

  • Use efficient cache lifetimes

    300 ms · 285 KiB

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

  • firespring.com adds 221 ms

    221 ms

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

  • Reduce unused CSS

    300 ms · 55 KiB

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

  • Legacy JavaScript

    300 ms · 32 KiB

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

  • Main-thread work: 2.8 s

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

  • 16 long tasks on the main thread

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

  • Improve image delivery

    150 ms · 52 KiB

    3 images could be 52 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.

  • Font display

    150 ms

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

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

  • Forced reflow

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

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

6 to fix45
  • Largest Contentful Paint: 11.6 s

    11.6 s

    Your largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Let us bring your best ideas to life. From concept to finis…”.

  • Time to Interactive: 20.4 s

    20.4 s

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

  • First Contentful Paint: 4.9 s

    4.9 s

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

  • Total Blocking Time: 844 ms

    844 ms

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

  • Speed Index: 6.7 s

    6.7 s

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

  • 1 image without width and height

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

  • Largest content (LCP) held steady for real visitors

    -5%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.7 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • 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

    0

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

Images and page weight

2 to fix55
  • Page weight: 5.0 MB in 149 requests

    5.0 MB

    Your homepage downloads 5.0 MB in 149 requests on a phone: images 2.6 MB (46), scripts 1.9 MB (35) and fonts 387 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    a9aec2fb-7d13-41d7-8c90-64804e442beb.jpg weighs 585 KiB. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (34 KiB) is 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.

  • About 1.4 g of CO₂ per visit

    1.41 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 7688
  • Images must have alternative text (2 elements)

    Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

  • Links look like plain text

    4 links inside paragraphs rely on colour alone to stand out.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 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 (6 elements)

    All page content should be contained by landmarks: 6 elements on the page fail 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.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 40 automated accessibility rules passed

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

SEO

1 to fixGoogle 9295
  • Meta description is long (246 characters)

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

  • 101 internal links, 13 external

    The homepage links to 101 pages on impressionsprinting.com and 13 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Learn about our”.

  • Title: 31 characters

    Your title is a healthy 31 characters: “Oklahoma City Printing Services”.

  • Canonical URL set

    The canonical URL is https://www.impressionsprinting.com/.

  • Structured data in place

    Structured data found: BreadcrumbList and LocalBusiness.

  • Open Graph tags complete

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

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.impressionsprinting.com/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, sameAs (social profiles), description and contact details; logo would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.impressionsprinting.com/llms.txt (18 KiB, 150 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix86
  • 2 pages share a title

    https://www.impressionsprinting.com/servicecenter and https://www.impressionsprinting.com/servicecenter/products_services.html all use the title “business cards|posters|banners|brochures|Oklahoma City|Ok”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.impressionsprinting.com/companyinfo/employment.html and https://www.impressionsprinting.com/companyinfo/employees.html use the same meta description. A description written for each page earns more clicks.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.impressionsprinting.com/specialties, whose canonical is https://www.impressionsprinting.com/specialties/banners.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page slow to respond

    https://www.impressionsprinting.com/companyinfo/employment.html took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8891
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: ev.data.startsWith is not a function”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 4 low-resolution images

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix89
  • No call to action on the first screen

    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 map or directions link

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

  • 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 275 words of copy

    The homepage carries about 275 words of visible text.

8 checks passed
  • 17 calls to action

    The homepage has 17 calls to action, for example “Get Started”, “Request An Estimate” and “Place A New Order”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 2 testimonial or review blocks and 2 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 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.

  • 30 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on impressionsprinting.com, including 16 speed issues, 1 SEO issue 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