Website review, no card needed

apcosigns.com logo

apcosigns.com website review

Visit site (opens in a new tab)Reviewed 23 October 202637 issues · 81 checks

This review found 37 issues worth fixing on apcosigns.com, 14 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. 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
2.6 s2.1 sMay 2Oct 172.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.4 s
May 9, 20262.4 s
May 16, 20262.4 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.3 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.5 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.6 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
115 ms73 msMay 2Oct 1779 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202693 ms
May 9, 202696 ms
May 16, 2026103 ms
May 23, 2026110 ms
May 30, 2026102 ms
Jun 6, 202697 ms
Jun 13, 2026102 ms
Jun 20, 202697 ms
Jun 27, 202691 ms
Jul 4, 202699 ms
Jul 11, 202691 ms
Jul 18, 202687 ms
Jul 25, 202696 ms
Aug 1, 202698 ms
Aug 8, 2026104 ms
Aug 15, 2026102 ms
Aug 22, 202698 ms
Aug 29, 202696 ms
Sep 5, 202692 ms
Sep 12, 202687 ms
Sep 19, 202688 ms
Sep 26, 202682 ms
Oct 3, 202678 ms
Oct 10, 202682 ms
Oct 17, 202679 ms

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 apcosigns.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. apcosigns.com at 0.4 s0.4 s
  2. apcosigns.com at 0.8 s0.8 s
  3. apcosigns.com at 1.1 s1.1 s
  4. apcosigns.com at 1.5 s1.5 s
  5. apcosigns.com at 1.9 s1.9 s
  6. apcosigns.com at 2.3 s2.3 s
  7. apcosigns.com at 2.6 s2.6 s
  8. apcosigns.com at 3.0 s3.0 s

Speed

3 to fix65
  • Use efficient cache lifetimes

    77.3 s · 22.3 MB

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

  • Improve image delivery

    54.5 s · 13.1 MB

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

  • Mobile performance score: 65

    65/100

    Your mobile performance score is 65 (desktop: 81). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    150 ms · 28 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Google CDN and Bootstrap CDN and others), adding 243 KiB and 138 ms of main-thread time.

  • Render-blocking requests

    150 ms

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

  • Reduce unused JavaScript

    97 KiB

    About 97 KiB of JavaScript is downloaded but never used on this page.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 83 ms. During a long task the page ignores taps.

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

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.3 s

    A phone's processor spends 0.3 s on main-thread work while loading, 121 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

7 to fix100
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 107.0 s

    107.0 s

    Your largest element takes 107.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Architectural Signs and Wayfinding Since 1966”.

  • Time to Interactive: 109.4 s

    109.4 s

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

  • Speed Index: 6.4 s

    6.4 s

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

    The first text or image appears after 2.8 s on a phone. Good is under 1.8 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

    -1%

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

7 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 116 ms

    116 ms

    Real visitors wait 116 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Tap response (INP) got 15% faster for real visitors

    -15%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 33 ms

    33 ms

    Scripts block the page for only 33 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix18
  • Page weight: 22.5 MB in 47 requests

    22.5 MB

    Your homepage downloads 22.5 MB in 47 requests on a phone: images 22.2 MB (36), scripts 268 KiB (7) and stylesheets 37 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 11 images over 500 KB

    11 images weigh 19.0 MB together. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    10.4 MB

    1 image is downloaded at several times the size a phone draws it, for example durham-hall-letters2.jpg at 5,979 px wide, shown at 360 px. Resized copies would save about 10.4 MB.

  • 28 images in older formats

    28 images (22.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.

  • 8 images below the first screen load straight away

    8 images further down the page (2.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 6.4 g of CO₂ per visit

    6.39 g

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

Accessibility

8 to fixGoogle 8188
  • 11 text elements with low contrast

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

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

    All page content should be contained by landmarks: 7 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.

  • Page should contain a level-one heading (1 element)

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

  • 6 links without text

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

  • 1 form field without a label

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

2 checks passed
  • Every image has alt text

    All 43 images in the HTML carry an alt attribute.

  • 32 automated accessibility rules passed

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

SEO

5 to fixGoogle 10077
  • No H1 headline

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

  • No structured data

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

  • Meta description is long (331 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 102 internal links, 4 external

    The homepage links to 102 pages on apcosigns.com and 4 external pages.

4 checks passed
  • Title: 49 characters

    Your title is a healthy 49 characters: “APCO Signs: Architectural Sign Systems Since 1966”.

  • Canonical URL set

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

  • 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.apcosigns.com/sitemap.xml.

AI search readiness

1 to fix83
  • 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://www.apcosigns.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.

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

Other pages

2 to fix90
  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.apcosigns.com/apco-tips-signage.html, whose canonical is https://www.apcosigns.com/apco-gsa.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://www.apcosigns.com/contactus.html and https://www.apcosigns.com/faq.html have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.apcosigns.com/apco-linkedin.html and https://www.apcosigns.com/faq.html have 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 59 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.

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8887
  • 8 small tap targets

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

  • 1 JavaScript error while loading

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

  • 5 low-resolution images

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 146 words

    The homepage has only about 146 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Order SignWord Paper”, “Contact Us” and “Request Information”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Ketch) is installed; check it blocks these until visitors agree where the law requires it.

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

1 checks passed
  • Consent tool: Ketch

    A consent management tool (Ketch) loads with the page.

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on apcosigns.com, including 10 speed issues, 5 SEO issues and 4 conversion gaps. 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