Website review, no card needed

admin.buildasign.com logo

admin.buildasign.com website review

Visit site (opens in a new tab)Reviewed 17 November 202640 issues · 81 checks

This review found 40 issues worth fixing on admin.buildasign.com, 12 of them high impact, across 81 checks. The most urgent: improve image delivery. 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 admin.buildasign.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix57
  • Improve image delivery

    2.8 s · 673 KiB

    20 images could be 673 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.8 s faster on a phone.

  • Render-blocking requests

    2.9 s

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

  • Reduce unused CSS

    1.1 s · 205 KiB

    About 205 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 57

    57/100

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

  • Minify CSS

    620 ms · 123 KiB

    123 KiB could be saved by minifying CSS.

  • 5 long tasks on the main thread

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

  • Google Tag Manager adds 305 ms

    305 ms

    Google Tag Manager costs a phone 305 ms of main-thread work and 395 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, New Relic and VWO and others), adding 476 KiB and 351 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 176 KiB

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

  • Minify JavaScript

    150 ms · 76 KiB

    76 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    17 KiB

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

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

2 checks passed
  • Main-thread work: 1.6 s

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

  • Server response: 54 ms

    54 ms

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

Core Web Vitals

6 to fix58
  • Largest Contentful Paint: 9.5 s

    9.5 s

    Your largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “CREATE CUSTOM SIGNS IN MINUTES”.

  • Time to Interactive: 11.6 s

    11.6 s

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

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • 36 images without width and height

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

  • Speed Index: 4.6 s

    4.6 s

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

  • Total Blocking Time: 328 ms

    328 ms

    Scripts block taps and scrolling for 328 ms 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

    0

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

Images and page weight

2 to fix75
  • Page weight: 3.2 MB in 113 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 113 requests on a phone: images 1.5 MB (39), other files 735 KiB (42) and scripts 630 KiB (21). Under 2 MB keeps phones on slow connections fast.

  • 10 images in older formats

    10 images (989 KiB) 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.

  • 5 images below the first screen load straight away

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

  • About 0.9 g of CO₂ per visit

    0.90 g

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

1 checks passed
  • 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 7788
  • 5 tap targets too small

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

  • 7 form fields without a label

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

  • 3 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 47 images in the HTML carry an alt attribute.

  • 31 automated accessibility rules passed

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

SEO

6 to fixGoogle 6166
  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • No structured data

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

  • 3 H1 headlines

    There are 3 <h1> headlines (“Create Custom Signs in Minutes!”, “Create Custom Signs in Minutes!” and “Create Custom Signs in Minutes!”). One clear main headline is easier for people and search engines.

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

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

  • 235 internal links, 19 external

    The homepage links to 235 pages on admin.buildasign.com and 19 external pages.

4 checks passed
  • Meta description: 133 characters

    Your meta description is 133 characters: “Custom Signs - 100% customer satisfaction guarantee! BuildASign is the #1 leading custom signs expert. SHIPS NEXT DAY! …”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Custom Signs, Banners, Flags | 25% OFF + FREE Shipping”.

  • Canonical URL set

    The canonical URL is https://admin.buildasign.com/.

  • XML sitemap found

    Your XML sitemap is reachable at https://admin.buildasign.com/sitemap.xml.

AI search readiness

2 to fix53
  • robots.txt blocks 6 AI answer engine crawlers

    6 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • 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://admin.buildasign.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

1 checks passed
  • Text is in the HTML

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

Other pages

5 to fix74
  • 13 linked pages hidden from search

    https://admin.buildasign.com/PricingCalculatorWithOptions.aspx, https://admin.buildasign.com/Help, https://admin.buildasign.com/HelpID.aspx, https://admin.buildasign.com/personalized-signs, https://admin.buildasign.com/custom-signs and https://admin.buildasign.com/yard-signs and 7 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://admin.buildasign.com/personalized-signs and https://admin.buildasign.com/custom-signs all use the title “Custom Signs & Yard Signs | 20% OFF + FREE Shipping”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://admin.buildasign.com/PricingCalculatorWithOptions.aspx, https://admin.buildasign.com/Help, https://admin.buildasign.com/HelpID.aspx and https://admin.buildasign.com/aluminum-signs have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://admin.buildasign.com/personalized-signs and https://admin.buildasign.com/custom-signs use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://admin.buildasign.com/Help and https://admin.buildasign.com/HelpID.aspx have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 8893
  • 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 400 ()”.

  • 6 low-resolution images

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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.

  • Thin social proof

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • About 649 words of copy

    The homepage carries about 649 words of visible text.

3 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Corporate Pricing”, “Call Us” and “Start »”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads 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.

  • 12 cookies set on arrival

    12

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

  • 17 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
CloudFront

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on admin.buildasign.com, including 13 speed issues, 6 SEO issues and 2 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
admin.buildasign.com website review: scores and fixes