Website review, no card needed

oldgloryflagpole.com logo

oldgloryflagpole.com website review

Visit site (opens in a new tab)Reviewed 7 November 202625 issues · 74 checks

This review found 25 issues worth fixing on oldgloryflagpole.com, 9 of them high impact, across 74 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

Real-visitor load time (LCP)75th percentile, phones
1.2 s846 msMay 16Oct 31954 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.0 s
May 23, 2026968 ms
May 30, 2026921 ms
Jun 6, 2026897 ms
Jun 13, 2026885 ms
Jun 20, 2026894 ms
Jun 27, 2026897 ms
Jul 4, 2026898 ms
Jul 11, 2026916 ms
Jul 18, 2026923 ms
Jul 25, 2026962 ms
Aug 1, 2026977 ms
Aug 8, 2026984 ms
Aug 15, 20261.0 s
Aug 22, 20261.0 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 2026990 ms
Oct 10, 2026960 ms
Oct 17, 2026941 ms
Oct 24, 2026946 ms
Oct 31, 2026954 ms
Real-visitor tap response (INP)75th percentile, phones
95 ms78 msMay 16Oct 3180 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202693 ms
May 23, 202693 ms
May 30, 202691 ms
Jun 6, 202689 ms
Jun 13, 202689 ms
Jun 20, 202689 ms
Jun 27, 202689 ms
Jul 4, 202688 ms
Jul 11, 202688 ms
Jul 18, 202687 ms
Jul 25, 202687 ms
Aug 1, 202684 ms
Aug 8, 202681 ms
Aug 15, 202683 ms
Aug 22, 202683 ms
Aug 29, 202687 ms
Sep 5, 202687 ms
Sep 12, 202687 ms
Sep 19, 202688 ms
Sep 26, 202687 ms
Oct 3, 202688 ms
Oct 10, 202683 ms
Oct 17, 202683 ms
Oct 24, 202683 ms
Oct 31, 202680 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 oldgloryflagpole.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix55
  • Reduce unused JavaScript

    6.4 s · 898 KiB

    About 898 KiB 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

    3.9 s

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

  • Improve image delivery

    950 ms · 430 KiB

    12 images could be 430 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Privy and Other Google APIs/SDKs and others), adding 1.8 MB and 909 ms of main-thread time.

  • Use efficient cache lifetimes

    900 ms · 119 KiB

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

  • Mobile performance score: 55

    55/100

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

  • Google CDN adds 501 ms

    501 ms

    Google CDN costs a phone 501 ms of main-thread work and 1.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.

  • Main-thread work: 3.2 s

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

  • Minify JavaScript

    150 ms · 4 KiB

    4 KiB could be saved by minifying JavaScript.

  • 10 long tasks on the main thread

    10 long tasks block the main thread while loading, the longest for 106 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.

  • 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: 7 ms

    7 ms

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

Core Web Vitals

4 to fix100
  • First Contentful Paint: 11.4 s

    11.4 s

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

  • Largest Contentful Paint: 19.0 s

    19.0 s

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

  • Time to Interactive: 20.9 s

    20.9 s

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

  • Speed Index: 11.4 s

    11.4 s

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.1 s

    1.1 s

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

  • Real-user INP: 71 ms

    71 ms

    Real visitors wait 71 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.0 s

    1.0 s

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

  • Real-user TTFB: 571 ms

    571 ms

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

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

    -12%

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

  • Total Blocking Time: 106 ms

    106 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix83
  • Page weight: 3.9 MB in 196 requests

    3.9 MB

    Your homepage downloads 3.9 MB in 196 requests on a phone: scripts 1.8 MB (62), other files 982 KiB (65) and images 783 KiB (21). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    30_-Great-4-pano_4e99260e-9515-4f43-a6a5-51f0635e4f7e.jpg 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).

  • 1 image in older formats

    1 image (53 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.

  • 4 images below the first screen load straight away

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

  • About 1.1 g of CO₂ per visit

    1.11 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.11 g of CO₂e: 132.7 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

4 to fixGoogle 9695
  • Scrollable region must have keyboard access (3 elements)

    Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • 8 links without text

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

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 53 automated accessibility rules passed

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

SEO

3 to fixGoogle 9287
  • Meta description is long (308 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 107 internal links, 9 external

    The homepage links to 107 pages on oldgloryflagpole.com and 9 external pages.

5 checks passed
  • Title: 37 characters

    Your title is a healthy 37 characters: “Old Glory Flagpole – OldGloryFlagpole”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://oldgloryflagpole.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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://oldgloryflagpole.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 10 pages without a meta description

    https://oldgloryflagpole.com/collections/accessories-add-ons, https://oldgloryflagpole.com/collections/replacement-parts, https://oldgloryflagpole.com/collections/usa-country-flags, https://oldgloryflagpole.com/collections/military-flags, https://oldgloryflagpole.com/collections/state-flags and https://oldgloryflagpole.com/collections/political-religious-flags and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • 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

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 analytics detected

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

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

    The homepage carries about 439 words of visible text.

4 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact us”, “Learn more about the App” and “Contact information”.

  • 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: a star rating and 1 trust badge.

  • Direct contact links

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

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 Microsoft Ads (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.

  • 11 cookies set on arrival

    11

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

  • 22 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Plus
Hosting
Cloudflare

Company

Headquarters
Provo

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on oldgloryflagpole.com, including 12 speed issues, 3 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