Website review, no card needed

premierfiredoors.com logo

premierfiredoors.com website review

Visit site (opens in a new tab)Reviewed 10 November 202633 issues · 69 checks

This review found 33 issues worth fixing on premierfiredoors.com, 9 of them high impact, across 69 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
3.0 s1.1 sMay 23Nov 72.5 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.3 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20262.3 s
Sep 19, 20262.6 s
Sep 26, 20262.7 s
Oct 3, 20262.8 s
Oct 10, 20262.8 s
Oct 17, 20262.7 s
Oct 24, 20262.7 s
Oct 31, 20262.6 s
Nov 7, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
273 ms93 msMay 23Nov 7231 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026130 ms
May 30, 2026125 ms
Jun 6, 2026127 ms
Jun 13, 2026137 ms
Jun 20, 2026143 ms
Jun 27, 2026138 ms
Jul 4, 2026125 ms
Jul 11, 2026114 ms
Jul 18, 2026114 ms
Jul 25, 2026120 ms
Aug 1, 2026129 ms
Aug 8, 2026131 ms
Aug 15, 2026125 ms
Aug 22, 2026128 ms
Aug 29, 2026136 ms
Sep 5, 2026131 ms
Sep 12, 2026195 ms
Sep 19, 2026222 ms
Sep 26, 2026231 ms
Oct 3, 2026252 ms
Oct 10, 2026250 ms
Oct 17, 2026243 ms
Oct 24, 2026246 ms
Oct 31, 2026237 ms
Nov 7, 2026231 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 premierfiredoors.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. premierfiredoors.com at 0.4 s0.4 s
  2. premierfiredoors.com at 0.8 s0.8 s
  3. premierfiredoors.com at 1.2 s1.2 s
  4. premierfiredoors.com at 1.6 s1.6 s
  5. premierfiredoors.com at 2.0 s2.0 s
  6. premierfiredoors.com at 2.4 s2.4 s
  7. premierfiredoors.com at 2.8 s2.8 s
  8. premierfiredoors.com at 3.2 s3.2 s

Speed

4 to fix62
  • Reduce unused JavaScript

    1.1 s · 241 KiB

    About 241 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 62

    62/100

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

  • Render-blocking requests

    450 ms

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

  • Google CDN adds 108 ms

    108 ms

    Google CDN costs a phone 108 ms of main-thread work and 298 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 CDN, iconnode.com and Shopify and others), adding 722 KiB and 318 ms of main-thread time.

  • Use efficient cache lifetimes

    150 ms · 66 KiB

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

  • 2 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Reduce unused CSS

    20 KiB

    About 20 KiB of CSS is downloaded but never applied on this page.

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

  • Duplicated JavaScript

    3 KiB

    3 KiB JavaScript is shipped twice across bundles.

2 checks passed
  • Main-thread work: 1.0 s

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

  • Server response: 40 ms

    40 ms

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

Core Web Vitals

11 to fix33
  • 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: 9.0 s

    9.0 s

    Your largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “421 E DRACHMAN TUCSON AZ 85705-7598 USA”.

  • Time to Interactive: 9.0 s

    9.0 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Speed Index: 6.6 s

    6.6 s

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user INP: 286 ms

    286 ms

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

  • Tap response (INP) got 84% slower for real visitors

    +84%

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

  • Largest content (LCP) got 52% slower for real visitors

    +52%

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

  • Real-user FCP: 2.6 s

    2.6 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

3 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Total Blocking Time: 82 ms

    82 ms

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

  • Cumulative Layout Shift: 0.013

    0.013

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

Images and page weight

100
  • About 0.3 g of CO₂ per visit

    0.33 g

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

1 checks passed
  • Page weight: 1.2 MB in 87 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 87 requests on a phone: scripts 692 KiB (51), fonts 273 KiB (7) and stylesheets 88 KiB (12). That is a lean page.

Accessibility

3 to fixGoogle 8184
  • 5 text elements with low contrast

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings skip levels

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

1 checks passed
  • 13 automated accessibility rules passed

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

SEO

5 to fixGoogle 10076
  • Title is long (89 characters)

    Your title is 89 characters, so Google will cut it off around 60: “FD30 Fire Doors | Internal & External Doors | FD60 Glazed Door Pairs – Premier Fire Doors”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Current Testing Standards”). One clear main headline is easier for people and search engines.

  • Meta description is long (258 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

  • No social preview image

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

  • 85 internal links, 5 external

    The homepage links to 85 pages on premierfiredoors.com and 5 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.premierfiredoors.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.premierfiredoors.com/sitemap.xml.

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

  • llms.txt published

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

Other pages

4 to fix83
  • 7 pages without a meta description

    https://www.premierfiredoors.com/pages/fire-doorsets-landing-page, https://www.premierfiredoors.com/collections/frames-architraves, https://www.premierfiredoors.com/collections/mendes-jb-kind-unity-doors, https://www.premierfiredoors.com/pages/pas24-fire-doors, https://www.premierfiredoors.com/pages/non-pas24-fire-doorsets and https://www.premierfiredoors.com/collections/zoo-hardware-ironmongery and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages share a meta description

    https://www.premierfiredoors.com/pages/fire-door-catalogue, https://www.premierfiredoors.com/pages/compliance-hub-1 and https://www.premierfiredoors.com/pages/composite-fire-doors use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.premierfiredoors.com/products/fire-door-foam%E2%84%A2-750ml, whose canonical is https://www.premierfiredoors.com/products/fire-door-foam%e2%84%a2-750ml. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 9 pages without an H1

    https://www.premierfiredoors.com/pages/fire-door-catalogue, https://www.premierfiredoors.com/pages/fire-doorsets-landing-page, https://www.premierfiredoors.com/pages/compliance-hub-1, https://www.premierfiredoors.com/pages/fd90-fd120-fire-doors, https://www.premierfiredoors.com/pages/composite-fire-doors and https://www.premierfiredoors.com/pages/pas24-fire-doors and 3 others 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 49 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

1 to fixGoogle 9692
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Error processing cart: TypeError: Failed to fetch”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 23 words

    The homepage has only about 23 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.

4 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Apply for Credit”, “Contact Us” and “Subscribe”.

  • 4 short forms

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

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Microsoft Clarity (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.

  • 9 cookies set on arrival

    9

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

  • 15 other companies contacted

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

Apps on your store

Your storefront loads 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Whatconverts · Judge Me Reviews · Blockx Country Blocker · Inbox · Microsoft Clarity · Google Youtube · cloudfront.net · webyze.com · good-apps.co

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Company

Headquarters
Derby

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on premierfiredoors.com, including 15 speed issues, 5 SEO issues and 3 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