fbflurry.com website review

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

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

Your mobile performance score is 45 (desktop: 100). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google Tag Manager, cloudfront.net and Optanon and others), adding 2.3 MB and 2.0 s of main-thread time.

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

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

cloudfront.net costs a phone 372 ms of main-thread work and 452 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.

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

About 103 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.

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

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

Polyfills for old browsers add 32 KiB JavaScript that modern phones do not need.

Desktop scores 100 but mobile only 45. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

Your largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Manage inventory, orders and nationwide fulfillment so fast…”.

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

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

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

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

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

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

Your homepage downloads 12.3 MB in 223 requests on a phone: media 7.1 MB (1), scripts 2.6 MB (54) and images 2.1 MB (58). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example Blog_pick-pathing.jpg at 1,920 px wide, shown at 255 px. Resized copies would save about 999 KiB.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 194 pages on fbflurry.com and 10 external pages.

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.

There is no /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.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343152219&tm=gtm002&Ver=2&mid=4eb1c931-01c4-4743-ac5c-28df0db624dd&bo=1&sid=20b26990cfe011f181832b4dafc086dd&vid=20b28d00cfe011f1a3e433ade8092257&vids=1&msclkid=N&gtm_.

The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

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

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

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

Large scripts ship without source maps.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

Opening https://fbflurry.com goes through 2 redirects before the homepage loads.

2 links go through two or more redirects, for example https://cta-service-cms2.hubspot.com/web-interactives/public/v1/track/click?encryptedPayload=AVxigLL9vcBuXF5xm%2BKSTEgTc%2Fj7wzElohr6eVCCiev7a5CkfgdF4CylstDjxt6BO1lWgxoEwhfc5zknj7BqPUPN4WSXuc0EzSMZcwYVVQpWm8FzOBRLekAvjmWCTd1d8hyuCUWnn8C4uJm7oIVmH9KQIh1snCqxefEoUUt0uO8IL3FkArJQd1VmaYLBb8R21Ch5HA%3D%3D&portalId=23181990.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

cart.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

cart.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

fbflurry.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 22 cookies, 1 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 52 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.