Website review, no card needed

biglive.com logo

biglive.com website review

Visit site (opens in a new tab)Reviewed 19 November 202655 issues · 96 checks

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

Full-page screenshot of biglive.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. biglive.com at 1.5 s1.5 s
  2. biglive.com at 3.0 s3.0 s
  3. biglive.com at 4.5 s4.5 s
  4. biglive.com at 6.0 s6.0 s
  5. biglive.com at 7.5 s7.5 s
  6. biglive.com at 9.0 s9.0 s
  7. biglive.com at 10.5 s10.5 s
  8. biglive.com at 12.0 s12.0 s

Speed

12 to fix30
  • Reduce unused JavaScript

    17.1 s · 2.9 MB

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

  • Reduce unused CSS

    7.9 s · 1.1 MB

    About 1.1 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 7.9 s faster on a phone.

  • Render-blocking requests

    8.9 s

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

  • Use efficient cache lifetimes

    1.9 s · 4.8 MB

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

  • YouTube adds 3.2 s

    3.2 s

    YouTube costs a phone 3.2 s of main-thread work and 4.9 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.

  • Mobile performance score: 30

    30/100

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

  • Main-thread work: 9.6 s

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

  • Improve image delivery

    550 ms · 8.5 MB

    36 images could be 8.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Facebook and Google Tag Manager and others), adding 5.8 MB and 3.7 s of main-thread time.

  • 20 long tasks on the main thread

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

  • 1,675 HTML elements

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

  • Cloudflare CDN adds 17 ms

    17 ms

    Cloudflare CDN costs a phone 17 ms of main-thread work and 305 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.

  • Minify CSS

    260 ms · 66 KiB

    66 KiB could be saved by minifying CSS.

  • Minify JavaScript

    55 KiB

    55 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

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

  • Legacy JavaScript

    11 KiB

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

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

    487 ms

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

Core Web Vitals

6 to fix39
  • First Contentful Paint: 9.4 s

    9.4 s

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

  • Largest Contentful Paint: 53.7 s

    53.7 s

    Your largest element takes 53.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Gujarat the land of strategy”.

  • Speed Index: 35.3 s

    35.3 s

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

  • Time to Interactive: 93.3 s

    93.3 s

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

  • Total Blocking Time: 1.4 s

    1.4 s

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

  • 1 image without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0.017

    0.017

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

Images and page weight

5 to fix18
  • Page weight: 22.1 MB in 170 requests

    22.1 MB

    Your homepage downloads 22.1 MB in 170 requests on a phone: images 10.4 MB (57), scripts 5.1 MB (38) and media 3.2 MB (1). Under 2 MB keeps phones on slow connections fast.

  • 26 images far larger than shown

    7.3 MB

    26 images are downloaded at several times the size a phone draws them, for example top-5-mantra-of-gujaratis for.png at 1,280 px wide, shown at 41 px. Resized copies would save about 7.3 MB.

  • 3 images over 500 KB

    3 images weigh 5.6 MB together. On a phone connection a single image that size takes seconds.

  • 11 images in older formats

    11 images (6.7 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.

  • 11 images below the first screen load straight away

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

  • About 6.3 g of CO₂ per visit

    6.27 g

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

Accessibility

12 to fixGoogle 7584
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 14 tap targets too small

    14 tap targets are too small or too close together to hit reliably with a finger.

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

  • Orphan list items

    Some list items are not inside a list.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (29 elements)

    All page content should be contained by landmarks: 29 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 6 links without text

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (2 elements)

    Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

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

2 checks passed
  • Every image has alt text

    All 68 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

5 to fixGoogle 9278
  • No H1 headline

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

  • No structured data

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

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

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

  • 2 links crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 269 internal links, 3 external

    The homepage links to 269 pages on biglive.com and 3 external pages.

4 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Get in touch with BigLive, your go-to source for the latest in news, technology, lifestyle, food, travel, real estate, …”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Big Live: Property News, Fitness & Food Guide”.

  • Canonical URL set

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

  • XML sitemap found

    Your XML sitemap is reachable at https://biglive.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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 https://biglive.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.

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

4 to fix60
  • 2 linked pages are broken

    Your homepage links to https://biglive.com/punjab and https://biglive.com/tamil-nadu, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 13 pages point its canonical at the homepage

    https://biglive.com/andhra-pradesh, https://biglive.com/assam, https://biglive.com/bihar, https://biglive.com/delhi-ncr, https://biglive.com/goa and https://biglive.com/gujarat and 7 others declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 13 pages share a meta description

    https://biglive.com/andhra-pradesh, https://biglive.com/assam, https://biglive.com/bihar, https://biglive.com/delhi-ncr, https://biglive.com/goa and https://biglive.com/gujarat and 7 others use the same meta description. A description written for each page earns more clicks.

  • 13 pages without an H1

    https://biglive.com/andhra-pradesh, https://biglive.com/assam, https://biglive.com/bihar, https://biglive.com/delhi-ncr, https://biglive.com/goa and https://biglive.com/gujarat and 7 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 116 found) and read each the way a search engine does.

4 checks passed
  • Every page has a meta description

    All 13 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 13 pages that loaded have a <title>.

Best practices

4 to fixGoogle 6983
  • 8 small tap targets

    8 of 38 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://www.biglive.com/assets/fonts/icons.ttf?v=1.6.3' from origin 'https://biglive.com' has been b…”.

  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • 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.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

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

  • No direct contact details

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

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

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

    The homepage carries about 588 words of visible text.

3 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “10 Best Used Cars To Buy”, “Subscribe” and “Contact Us”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Comscore, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

  • 5 cookies set on arrival

    5

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

  • 18 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
jQuery
Analytics
Google Analytics
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 55 issues on biglive.com, including 18 speed issues, 5 SEO issues and 5 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