bigcom.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

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

• Real-user INP: 1.2 s

  1.2 s

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

• Real-user CLS: 0.40

  0.40

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

• Real-user LCP: 3.2 s

  3.2 s

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

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

  +46%

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

• Real-user FCP: 3.0 s

  3.0 s

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

• Real-user TTFB: 1.5 s

  1.5 s

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

• Tap response (INP) held steady for real visitors

  0%

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

• About 0.3 g of CO₂ per visit

  0.31 g

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

• 2 buttons without a name

  2 buttons have no accessible name, so screen readers announce just “button”.

  Elements (2)

• 2 text elements with low contrast

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

  Elements (2)

• Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

  Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• Zoom is disabled

  The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  Elements (1)

• 1 link without text

  1 visible link has no text or label, so screen readers cannot say where it goes.

  Elements (1)

• Headings skip levels

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

  View sourceElements (1)

• No H1 headline

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

• Title is short (15 characters)

  Your title is only 15 characters: “Hi :) | Big Com”. Between 30 and 65 characters leaves room to say what you do and for whom.

  View source

• No structured data

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

• No canonical URL

  No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

• No XML sitemap

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

• No robots.txt

  There is no robots.txt at bigcom.com/robots.txt, the first file search crawlers ask for.

• No X (Twitter) card tag

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

• 20 internal links, 4 external

  The homepage links to 20 pages on bigcom.com and 4 external pages.

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

• 1 page without a meta description

  /work/valvoline has no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (1)

• 2 pages share a meta description

  /work and /news use the same meta description. A description written for each page earns more clicks.

• 15 pages without an H1

  /work, /agency, /news, /work/made-in-alabama, /work/seek-alabama and /work/uab-callahan-eye and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

• 1 page slow to respond

  /work/alabama-department-of-workforce took over 3 s to send its HTML from our server.

• 15 internal pages checked

  We fetched 15 pages linked from your homepage and read each the way a search engine does.

• 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 404 ()”.

• http:// does not redirect

  http://bigcom.com does not redirect to https, so some visitors land on the insecure version.

• No Content-Security-Policy

  No Content-Security-Policy header, the main browser-side defence against injected scripts.

• No clickjacking protection

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

• 2 redirects before the homepage

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

• 1 link through redirect chains

  1 link go through two or more redirects, for example https://instagram.com/bigbhm.

• No Referrer-Policy

  No Referrer-Policy header, so full URLs can leak to the sites you link to.

• No Permissions-Policy

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

• No security.txt

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

• Domain expires in 33 days

  bigcom.com is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

• No CAA record

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

• DNSSEC is off

  bigcom.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 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 social proof

  No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

• No opening hours

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

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

• No map or directions link

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

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

  The homepage carries about 411 words of visible text.

• Email authentication score: 100/100

  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.

• 6 trackers load before any consent

  6

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Clarity and 1 more (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.

• 4 cookies set on arrival

  4

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

• 13 other companies contacted

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