Website review, no card needed

forbesindustries.com logo

forbesindustries.com website review

Visit site (opens in a new tab)Reviewed 20 October 202649 issues · 95 checks

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

Real-visitor load time (LCP)75th percentile, phones
4.1 s2.8 sAug 15Oct 174.0 s
Show as table
DateReal-visitor load time (LCP)
Aug 15, 20263.1 s
Aug 22, 20263.1 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20263.1 s
Sep 19, 20263.2 s
Sep 26, 20263.3 s
Oct 3, 20263.5 s
Oct 10, 20263.7 s
Oct 17, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
193 ms148 msAug 15Oct 17183 ms
Show as table
DateReal-visitor tap response (INP)
Aug 15, 2026153 ms
Aug 22, 2026159 ms
Aug 29, 2026161 ms
Sep 5, 2026170 ms
Sep 12, 2026174 ms
Sep 19, 2026181 ms
Sep 26, 2026188 ms
Oct 3, 2026183 ms
Oct 10, 2026184 ms
Oct 17, 2026183 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 forbesindustries.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. forbesindustries.com at 1.2 s1.2 s
  2. forbesindustries.com at 2.4 s2.4 s
  3. forbesindustries.com at 3.6 s3.6 s
  4. forbesindustries.com at 4.8 s4.8 s
  5. forbesindustries.com at 6.0 s6.0 s
  6. forbesindustries.com at 7.2 s7.2 s
  7. forbesindustries.com at 8.4 s8.4 s
  8. forbesindustries.com at 9.5 s9.5 s

Speed

16 to fix27
  • Improve image delivery

    14.6 s · 4.3 MB

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

  • Reduce unused JavaScript

    3.1 s · 1.7 MB

    About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

  • Use efficient cache lifetimes

    1.8 s · 632 KiB

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

  • Render-blocking requests

    1.8 s

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

  • Google CDN adds 1.5 s

    1.5 s

    Google CDN costs a phone 1.5 s of main-thread work and 2.2 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.

  • Main-thread work: 10.3 s

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

  • Mobile performance score: 27

    27/100

    Your mobile performance score is 27 (desktop: 26). 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 CDN, Google Tag Manager and Facebook and others), adding 3.7 MB and 3.4 s of main-thread time.

  • Google Tag Manager adds 654 ms

    654 ms

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

  • Reduce unused CSS

    470 ms · 115 KiB

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

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    350 ms · 42 KiB

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

  • Hubspot adds 333 ms

    333 ms

    Hubspot costs a phone 333 ms of main-thread work and 413 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.

  • Facebook adds 339 ms

    339 ms

    Facebook costs a phone 339 ms of main-thread work and 253 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.

  • Hotjar adds 310 ms

    310 ms

    Hotjar costs a phone 310 ms of main-thread work and 67 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.

  • 2,441 HTML elements

    The page has 2,441 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 15 ms

    15 ms

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

Core Web Vitals

10 to fix67
  • 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.

  • Real-user FCP: 3.3 s

    3.3 s

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

  • Real-user TTFB: 2.5 s

    2.5 s

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

  • Largest Contentful Paint: 41.3 s

    41.3 s

    Your largest element takes 41.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hotel bar service in a refined lobby”.

  • Speed Index: 24.9 s

    24.9 s

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

  • Time to Interactive: 53.4 s

    53.4 s

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

  • First Contentful Paint: 5.6 s

    5.6 s

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

  • Total Blocking Time: 2.3 s

    2.3 s

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

  • Real-user LCP: 4.0 s

    4.0 s

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

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

    +26%

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

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

    +18%

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

3 checks passed
  • Real-user INP: 183 ms

    183 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Cumulative Layout Shift: 0.046

    0.046

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

Images and page weight

6 to fix19
  • Page weight: 15.3 MB in 246 requests

    15.3 MB

    Your homepage downloads 15.3 MB in 246 requests on a phone: images 9.8 MB (79), scripts 4.0 MB (90) and other files 733 KiB (29). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 4.1 MB together. On a phone connection a single image that size takes seconds.

  • 10 images far larger than shown

    2.1 MB

    10 images are downloaded at several times the size a phone draws them, for example Firefly_Gemini-Flash_Luxury-hotel-conference-room-prepared-f at 1,376 px wide, shown at 402 px. Resized copies would save about 2.1 MB.

  • 14 images below the first screen load straight away

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

  • 10 images in older formats

    10 images (2.0 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.

  • An image on the first screen is lazy-loaded

    Firefly_Gemini-Flash_Luxury-hotel-conference-room-prepared-f 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).

  • About 4.3 g of CO₂ per visit

    4.34 g

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

Accessibility

6 to fixGoogle 9092
  • Elements must only use permitted ARIA attributes (3 elements)

    Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.

  • <svg> elements with an img or image role must have alternative text (3 elements)

    <svg> elements with an img or image role must have alternative text: 3 elements on the page fail this check, rated serious by axe-core.

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

  • 6 images without alt text

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

  • 3 links without text

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

  • Headings skip levels

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

1 checks passed
  • 54 automated accessibility rules passed

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

SEO

3 to fixGoogle 9284
  • No H1 headline

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

  • No XML sitemap

    No XML sitemap at https://www.forbesindustries.com/sitemap.xml, so Google discovers your pages only by following links.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 310 internal links, 7 external

    The homepage links to 310 pages on forbesindustries.com and 7 external pages.

6 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “Premium hospitality furniture, mobile bars, banquet tables, luggage carts, housekeeping carts, and food service equipme…”.

  • Title: 64 characters

    Your title is a healthy 64 characters: “Forbes Industries | Hospitality Furniture & Equipment Since 1919”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization, WebPage and WebSite.

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

AI search readiness

100
  • No llms.txt

    There is no https://www.forbesindustries.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.

3 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 (2,289 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 5 pages without an H1

    https://www.forbesindustries.com/trio-folding-mobile-action-station, https://www.forbesindustries.com/birdsnest-nestable-luggage-carts, https://www.forbesindustries.com/horizons-outdoor-mobile-furniture, https://www.forbesindustries.com/concept-to-reality and https://www.forbesindustries.com/food-beverage-solutions 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 73 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.

  • 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

3 to fixGoogle 7376
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97252621&tm=wpp_1.0.5&Ver=2&mid=791a4cc0-8f9b-4f81-a635-17bfc0db4816&bo=1&sid=5a4f0550cc6011f190444334fdc730fb&vid=5a4f4410cc6011f18745b30204aaffd7&vids=1&msclkid=N&pi.

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix78
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 5 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

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

  • About 1,165 words of copy

    The homepage carries about 1,165 words of visible text.

6 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “Contact Us”, “Sign up for our email list” and “Start Your Project”.

  • 2 short forms

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

  • Analytics in place

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

  • Direct contact links

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

  • Phone number on the homepage

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

  • 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
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 3 mores (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.

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 cookies, 1 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.

  • 44 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
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 49 issues on forbesindustries.com, including 26 speed issues, 3 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