Website review, no card needed

edgefullfibers.com logo

edgefullfibers.com website review

Visit site (opens in a new tab)Reviewed 6 November 202630 issues · 73 checks

This review found 30 issues worth fixing on edgefullfibers.com, 10 of them high impact, across 73 checks. The most urgent: use efficient cache lifetimes. 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
2.4 s2.0 sMay 30Aug 12.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Aug 1, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
140 ms122 msMay 30Jun 20138 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026124 ms
Jun 6, 2026127 ms
Jun 13, 2026138 ms
Jun 20, 2026138 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 edgefullfibers.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. edgefullfibers.com at 0.9 s0.9 s
  2. edgefullfibers.com at 1.8 s1.8 s
  3. edgefullfibers.com at 2.7 s2.7 s
  4. edgefullfibers.com at 3.6 s3.6 s
  5. edgefullfibers.com at 4.5 s4.5 s
  6. edgefullfibers.com at 5.4 s5.4 s
  7. edgefullfibers.com at 6.3 s6.3 s
  8. edgefullfibers.com at 7.2 s7.2 s

Speed

9 to fix47
  • Use efficient cache lifetimes

    1.9 s · 443 KiB

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

  • Reduce unused JavaScript

    1.9 s · 430 KiB

    About 430 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

  • Mobile performance score: 47

    47/100

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

  • Main-thread work: 5.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (amaicdn.com, Klaviyo and Shopify and others), adding 1.2 MB and 1.6 s of main-thread time.

  • amaicdn.com adds 654 ms

    654 ms

    amaicdn.com costs a phone 654 ms of main-thread work and 411 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.

  • Legacy JavaScript

    350 ms · 104 KiB

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

  • 17 long tasks on the main thread

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

  • Klaviyo adds 298 ms

    298 ms

    Klaviyo costs a phone 298 ms of main-thread work and 185 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.

  • Render-blocking requests

    150 ms

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

  • Improve image delivery

    61 KiB

    4 images could be 61 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    56 KiB

    About 56 KiB of CSS is downloaded but never applied on this page.

  • Minify CSS

    21 KiB

    21 KiB could be saved by minifying CSS.

  • 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

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

6 to fix45
  • Largest Contentful Paint: 9.0 s

    9.0 s

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

  • Time to Interactive: 14.2 s

    14.2 s

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

  • Total Blocking Time: 865 ms

    865 ms

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

  • Speed Index: 6.1 s

    6.1 s

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 24 images without width and height

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

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

    +10%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 124 ms to 138 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-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.0 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.

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix81
  • Page weight: 2.9 MB in 213 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 213 requests on a phone: scripts 1.3 MB (94), other files 738 KiB (79) and images 554 KiB (24). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    0S1A4585.png 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 0.8 g of CO₂ per visit

    0.81 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9696
  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

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

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

  • 2 links without text

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

2 checks passed
  • Every image has alt text

    All 66 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

2 to fixGoogle 10088
  • Title is short (14 characters)

    Your title is only 14 characters: “Curlkalon Hair”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 3 H1 headlines

    There are 3 <h1> headlines (“Curlkalon Hair”, “Wrap Braided Ponytail 22"” and “Wrap Braided Ponytail 22"”). One clear main headline is easier for people and search engines.

  • 93 internal links, 7 external

    The homepage links to 93 pages on edgefullfibers.com and 7 external pages.

6 checks passed
  • Meta description: 137 characters

    Your meta description is 137 characters: “Transform your style with Curlkalon's natural-looking, protective hair extensions. Consciously crafted for your hair's …”.

  • Canonical URL set

    The canonical URL is https://curlkalon.com/.

  • Structured data in place

    Structured data found: Product.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://curlkalon.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://curlkalon.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

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

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://curlkalon.com/products/curlkalon-soft-curl-10-clip-in-hair-extensions is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without an H1

    https://curlkalon.com/pages/store-locator has 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 36 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    7 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 7 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 7 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 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_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    13 of 15 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 495 words of visible text.

3 checks passed
  • 27 calls to action

    The homepage has 27 calls to action, for example “Contact Us”, “Where to Buy” and “Shop All icon-chevron Expand submenu”.

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 26 testimonial or review blocks and a star rating.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 18 cookies set on arrival

    18

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

  • 31 other companies contacted

    Loading the homepage contacts 31 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 edgefullfibers.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 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Yotpo Product Reviews · Eg Auto Add To Cart · Fabrikator Inventory Assistant · Product Labels And Badges · smile.io

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
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on edgefullfibers.com, including 15 speed issues, 2 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