Website review, no card needed

100acresbflo.com logo

100acresbflo.com website review

Visit site (opens in a new tab)Reviewed 18 November 202638 issues · 83 checks

This review found 38 issues worth fixing on 100acresbflo.com, 11 of them high impact, across 83 checks. The most urgent: render-blocking requests. 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.5 s3.3 sOct 3Oct 313.5 s
Show as table
DateReal-visitor load time (LCP)
Oct 3, 20263.5 s
Oct 10, 20263.4 s
Oct 17, 20263.4 s
Oct 24, 20263.5 s
Oct 31, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
471 ms377 msOct 3Oct 24388 ms
Show as table
DateReal-visitor tap response (INP)
Oct 3, 2026460 ms
Oct 10, 2026440 ms
Oct 17, 2026440 ms
Oct 24, 2026388 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 100acresbflo.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 100acresbflo.com at 0.7 s0.7 s
  2. 100acresbflo.com at 1.4 s1.4 s
  3. 100acresbflo.com at 2.1 s2.1 s
  4. 100acresbflo.com at 2.8 s2.8 s
  5. 100acresbflo.com at 3.5 s3.5 s
  6. 100acresbflo.com at 4.2 s4.2 s
  7. 100acresbflo.com at 5.0 s5.0 s
  8. 100acresbflo.com at 5.7 s5.7 s

Speed

10 to fix68
  • Render-blocking requests

    2.7 s

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

  • Improve image delivery

    500 ms · 2.5 MB

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

  • Reduce unused CSS

    900 ms · 1.5 MB

    About 1.5 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Mobile performance score: 68

    68/100

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

  • Reduce unused JavaScript

    750 ms · 158 KiB

    About 158 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Use efficient cache lifetimes

    200 ms · 372 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (istudiosg.com, Yellow Robot and Cloudflare and others), adding 1.3 MB and 209 ms of main-thread time.

  • Main-thread work: 3.2 s

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

  • istudiosg.com adds 172 ms

    172 ms

    istudiosg.com costs a phone 172 ms of main-thread work and 1.1 MB 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.

  • 1,800 HTML elements

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

  • Minify CSS

    150 ms · 16 KiB

    16 KiB could be saved by minifying CSS.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 72 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).

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 330 ms

    330 ms

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

Core Web Vitals

5 to fix67
  • Largest Contentful Paint: 9.4 s

    9.4 s

    Your largest element takes 9.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 12.1 s

    12.1 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Speed Index: 4.9 s

    4.9 s

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -8%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

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

2 checks passed
  • Cumulative Layout Shift: 0.028

    0.028

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

  • Total Blocking Time: 11 ms

    11 ms

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

Images and page weight

4 to fix25
  • Page weight: 4.1 MB in 105 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 105 requests on a phone: images 2.7 MB (18), fonts 582 KiB (7) and scripts 443 KiB (28). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    bannerasikdewislot77.png weighs 2.4 MB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    2.3 MB

    1 image is downloaded at several times the size a phone draws it, for example bannerasikdewislot77.png at 1,254 px wide, shown at 84 px. Resized copies would save about 2.3 MB.

  • 2 images in older formats

    2 images (2.4 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.

  • About 1.2 g of CO₂ per visit

    1.15 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

6 to fixGoogle 8491
  • 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.

  • 3 text elements with low contrast

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

  • 2 tap targets too small

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

  • 4 images without alt text

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

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

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

  • 1 link without text

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

  • Headings skip levels

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

1 checks passed
  • 50 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: 50 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 8584
  • 10 H1 headlines

    There are 10 <h1> headlines (“DewiSlot77 - Tempat Asik untuk Menikmati Dunia On…”, “DewiSlot77 - Tempat Asik untuk Menikmati Dunia On…” and “DewiSlot77 - Tempat Asik untuk Menikmati Dunia On…”). One clear main headline is easier for people and search engines.

  • Meta description is long (281 characters)

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

  • Structured data has 5 problems

    Structured data found (BreadcrumbList, FAQPage, Organization and Product) but with 5 problems, for example “Product: logo is not an absolute URL ("https://www.flceltic.org/highland-games/img/logodewislot77.png")”.

  • 3 links crawlers can't follow

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

  • 85 internal links, 79 external

    The homepage links to 85 pages on 100acresbflo.com and 79 external pages.

5 checks passed
  • Title: 61 characters

    Your title is a healthy 61 characters: “DewiSlot77 - Tempat Asik untuk Menikmati Dunia Online Sendiri”.

  • Canonical URL set

    The canonical URL is https://www.flceltic.org/highland-games/.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.flceltic.org/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

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

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

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

Other pages

3 to fix86
  • 16 pages share a title

    https://www.flceltic.org/highland-games, https://www.flceltic.org/policies/shipping-policy, https://www.flceltic.org/pages/applecare-landing-page, https://www.flceltic.org/products/iphone-17-pro-PLXQRTM-a, https://www.flceltic.org/pages/applecare and https://www.flceltic.org/pages/business-solutions and 10 others all use the title “DewiSlot77 - Tempat Asik untuk Menikmati Dunia Online Sendiri”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages share a meta description

    https://www.flceltic.org/policies/shipping-policy, https://www.flceltic.org/pages/applecare-landing-page, https://www.flceltic.org/products/iphone-17-pro-PLXQRTM-a, https://www.flceltic.org/pages/applecare, https://www.flceltic.org/pages/business-solutions and https://www.flceltic.org/pages/service-provider and 9 others use the same meta description. A description written for each page earns more clicks.

  • 15 links to non-canonical URLs

    Your homepage links to 15 pages by a URL that isn't their canonical one, for example https://www.flceltic.org/policies/shipping-policy, whose canonical is https://www.flceltic.org/highland-games. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page slow to respond

    https://www.flceltic.org/products/iphone-17-pro-PLXQRTM-a took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 8885
  • 10 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “SyntaxError: Failed to execute 'querySelector' on 'Document': '[object HTMLDocument]' is not a valid selector.”.

  • 7 distorted images

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 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 582 words of copy

    The homepage carries about 582 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Buy It Now”, “Contact Us” and “Why Shop at iStudio”.

  • 4 short forms

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

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, 4 customer or partner logos, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

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

  • 9 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 100acresbflo.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 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

backinstock.org

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
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on 100acresbflo.com, including 15 speed issues, 4 SEO issues and 2 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