Website review, no card needed
erafone.com website review
Visit site (opens in a new tab)Reviewed 22 October 202650 issues · 84 checks
This review found 50 issues worth fixing on erafone.com, 14 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
61DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.9 s |
| May 9, 2026 | 3.8 s |
| May 16, 2026 | 3.6 s |
| May 23, 2026 | 3.5 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.5 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 4.3 s |
| Aug 15, 2026 | 4.9 s |
| Aug 22, 2026 | 5.0 s |
| Aug 29, 2026 | 4.4 s |
| Sep 5, 2026 | 4.0 s |
| Sep 12, 2026 | 3.7 s |
| Sep 19, 2026 | 3.8 s |
| Sep 26, 2026 | 3.9 s |
| Oct 3, 2026 | 4.0 s |
| Oct 10, 2026 | 4.4 s |
| Oct 17, 2026 | 4.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 340 ms |
| May 9, 2026 | 345 ms |
| May 16, 2026 | 351 ms |
| May 23, 2026 | 356 ms |
| May 30, 2026 | 368 ms |
| Jun 6, 2026 | 378 ms |
| Jun 13, 2026 | 391 ms |
| Jun 20, 2026 | 399 ms |
| Jun 27, 2026 | 392 ms |
| Jul 4, 2026 | 388 ms |
| Jul 11, 2026 | 377 ms |
| Jul 18, 2026 | 372 ms |
| Jul 25, 2026 | 371 ms |
| Aug 1, 2026 | 390 ms |
| Aug 8, 2026 | 431 ms |
| Aug 15, 2026 | 473 ms |
| Aug 22, 2026 | 490 ms |
| Aug 29, 2026 | 485 ms |
| Sep 5, 2026 | 458 ms |
| Sep 12, 2026 | 435 ms |
| Sep 19, 2026 | 442 ms |
| Sep 26, 2026 | 447 ms |
| Oct 3, 2026 | 455 ms |
| Oct 10, 2026 | 452 ms |
| Oct 17, 2026 | 450 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
Speed
Reduce unused JavaScript
3.8 s · 736 KiBAbout 736 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.
Use efficient cache lifetimes
900 ms · 484 KiB8 files are served with short cache lifetimes, so returning visitors download them again (484 KiB).
Mobile performance score: 61
61/100Your mobile performance score is 61 (desktop: 47). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
800 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
8 third-party services on the page
8 third-party services load with your homepage (Facebook, Google Tag Manager and TikTok and others), adding 1.4 MB and 628 ms of main-thread time.
Improve image delivery
100 ms · 381 KiB7 images could be 381 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.
Legacy JavaScript
300 ms · 35 KiBPolyfills for old browsers add 35 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Facebook adds 219 ms
219 msFacebook costs a phone 219 ms of main-thread work and 314 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.
Google Tag Manager adds 195 ms
195 msGoogle Tag Manager costs a phone 195 ms of main-thread work and 345 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.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Other Google APIs/SDKs adds 17 ms
17 msOther Google APIs/SDKs costs a phone 17 ms of main-thread work and 469 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.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 195 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 43 KiBAbout 43 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.
Minify JavaScript
150 ms · 7 KiB7 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user CLS: 0.38
0.38For real visitors the layout shifts by 0.38 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 15.1 s
15.1 sYour largest element takes 15.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Erafone Teaser iPhone Duo - Mobile”.
Time to Interactive: 17.1 s
17.1 sThe page becomes fully interactive after 17.1 s. Good is under 3.8 s.
Speed Index: 7.6 s
7.6 sVisually, the page fills in at 7.6 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 444 ms
444 msReal visitors wait 444 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 32% slower for real visitors
+32%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 340 ms to 450 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 803 ms
803 msReal visitors wait 803 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 298 ms
298 msScripts block taps and scrolling for 298 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.9 s to 4.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
Images and page weight
Page weight: 2.5 MB in 112 requests
2.5 MBYour homepage downloads 2.5 MB in 112 requests on a phone: scripts 1.8 MB (52), images 572 KiB (23) and fonts 59 KiB (4). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
XCxZUbUZr5tNAkLqdqVpoJIcQZZGXrAy6dFyvsud.jpg 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).
3 images in older formats
3 images (366 KiB) 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 0.7 g of CO₂ per visit
0.71 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.71 g of CO₂e: 85.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
13 tap targets too small
13 tap targets are too small or too close together to hit reliably with a finger.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
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.
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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Positive tabindex
1 element has a tabindex above 0, which scrambles the keyboard order.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
2 checks passed
Every image has alt text
All 21 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Structured data has 2 problems
Structured data found ((untyped) and ProductCollection) but with 2 problems, for example “untyped block: missing @context (expected "https://schema.org")”.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
12 internal links, 0 external
The homepage links to 12 pages on erafone.com and 0 external pages.
5 checks passed
Meta description: 126 characters
Your meta description is 126 characters: “Beli Produk Gadget & Lifestyle Cicilan 0% | 100% Original | Garansi Resmi | Dapatkan Cashback MyEraspace Points | Bebas…”.
Title: 54 characters
Your title is a healthy 54 characters: “erafone.com | Pengalaman Belanja Online Terbaik & Aman”.
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://erafone.com/sitemap.xml.
AI search readiness
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://erafone.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.
1 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.
Other pages
5 pages share a title
/, https://erafone.com/katalog/pre-order-vivo-v80-lite-5g-11592, https://erafone.com/katalog/first-sales-huawei-watch-gt-7-series-11444, https://erafone.com/katalog/promo-iqoo-z11-11611 and https://erafone.com/katalog/first-selling-oppo-a7-pro-11463 all use the title “erafone.com | Pengalaman Belanja Online Terbaik & Aman”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://erafone.com/page/promo-samsung-galaxy-a18-release, https://erafone.com/page/lamina-iphone-18-pro-series and https://erafone.com/page/clearance-smartphone-preowned have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://erafone.com/katalog/pre-order-vivo-v80-lite-5g-11592, https://erafone.com/katalog/first-sales-huawei-watch-gt-7-series-11444, https://erafone.com/katalog/promo-iqoo-z11-11611 and https://erafone.com/katalog/first-selling-oppo-a7-pro-11463 use the same meta description. A description written for each page earns more clicks.
11 pages without an H1
https://erafone.com/page/iphone-18-pro-release, https://erafone.com/page/promo-samsung-galaxy-a18-release, https://erafone.com/page/promo-samsung-galaxy-a08-release, https://erafone.com/page/promo-samsung-galaxy-tab-s12-release, https://erafone.com/katalog/pre-order-vivo-v80-lite-5g-11592 and https://erafone.com/page/lamina-iphone-18-pro-series and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
8 pages with very little text
https://erafone.com/page/iphone-18-pro-release, https://erafone.com/katalog/pre-order-vivo-v80-lite-5g-11592, https://erafone.com/page/lamina-iphone-18-pro-series, https://erafone.com/katalog/first-sales-huawei-watch-gt-7-series-11444, https://erafone.com/katalog/promo-iqoo-z11-11611 and https://erafone.com/produk/lamina-plus-tempered-glass-for-samsung-a18-a17-a16 and 2 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
12 internal pages checked
We fetched 12 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 12 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
13 small tap targets
13 of 42 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 “Failed to load resource: the server responded with a status of 403 ()”.
Requests the geolocation permission on page load
Requests the geolocation permission on page load.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 59 words
The homepage has only about 59 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 2 mores (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
18Opening the homepage sets 18 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.
25 other companies contacted
Loading the homepage contacts 25 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 erafone.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 50 issues on erafone.com, including 22 speed issues, 3 SEO issues and 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.