Website review, no card needed
afewwoodmen.com website review
Visit site (opens in a new tab)Reviewed 17 November 202663 issues · 100 checks
This review found 63 issues worth fixing on afewwoodmen.com, 28 of them high impact, across 100 checks. The most urgent: mobile performance score: 28. 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
58FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.8 s |
| Oct 31, 2026 | 2.7 s |
| Nov 7, 2026 | 2.6 s |
| Nov 14, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jul 25, 2026 | 396 ms |
| Aug 1, 2026 | 400 ms |
| Aug 8, 2026 | 426 ms |
| Aug 15, 2026 | 445 ms |
| Aug 22, 2026 | 453 ms |
| Aug 29, 2026 | 479 ms |
| Sep 5, 2026 | 493 ms |
| Sep 12, 2026 | 510 ms |
| Sep 19, 2026 | 319 ms |
| Sep 26, 2026 | 247 ms |
| Oct 3, 2026 | 263 ms |
| Oct 10, 2026 | 436 ms |
| Oct 17, 2026 | 626 ms |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.3 s |
| Nov 7, 2026 | 1.0 s |
| Nov 14, 2026 | 576 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
How it loaded on a phone
0.9 s
1.8 s
2.7 s
3.6 s
4.6 s
5.5 s
6.4 s
7.3 s
Speed
Mobile performance score: 28
28/100Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,037 HTML elements
The page has 4,037 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
4.6 MB3 images could be 4.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
150 ms · 4.4 MB58 files are served with short cache lifetimes, so returning visitors download them again (4.4 MB).
8 third-party services on the page
8 third-party services load with your homepage (Adobe Tag Manager, Facebook and Google Maps and others), adding 1.9 MB and 1.3 s of main-thread time.
Reduce unused JavaScript
1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page.
Render-blocking requests
850 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 263 ms. During a long task the page ignores taps.
Google Maps adds 190 ms
190 msGoogle Maps costs a phone 190 ms of main-thread work and 329 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.
sprinklr.com adds 178 ms
178 mssprinklr.com costs a phone 178 ms of main-thread work and 432 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 CDN adds 121 ms
121 msGoogle CDN costs a phone 121 ms of main-thread work and 352 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
200 ms · 39 KiBPolyfills for old browsers add 39 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Minify JavaScript
7 KiB7 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 8 ms
8 msYour server sent the HTML in 8 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 INP: 557 ms
557 msReal visitors wait 557 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.48
0.48For real visitors the layout shifts by 0.48 (75th percentile). Good is under 0.1.
Speed Index: 15.7 s
15.7 sVisually, the page fills in at 15.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 24.1 s
24.1 sThe page becomes fully interactive after 24.1 s. Good is under 3.8 s.
First Contentful Paint: 5.4 s
5.4 sThe first text or image appears after 5.4 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.446
0.446The layout shifts by 0.446 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 5.4 s
5.4 sYour largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Cari Cari Troli Login Buka Menu Saya Navigation”. Most of its time is element render delay (2.3 s).
Tap response (INP) got 100% slower for real visitors
+100%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 396 ms to 576 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: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
109 images without width and height
109 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 502 ms
502 msScripts block taps and scrolling for 502 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Images and page weight
Page weight: 7.4 MB in 167 requests
7.4 MBYour homepage downloads 7.4 MB in 167 requests on a phone: images 5.0 MB (15), scripts 2.2 MB (83) and HTML 85 KiB (7). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
gif-2.gif weighs 2.1 MB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
1.5 MB1 image is downloaded at several times the size a phone draws it, for example gif-2.gif at 720 px wide, shown at 130 px. Resized copies would save about 1.5 MB.
1 image in older formats
1 image (2.1 MB) is 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 2.1 g of CO₂ per visit
2.10 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.10 g of CO₂e: 252.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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
152 tap targets too small
152 tap targets are too small or too close together to hit reliably with a finger.
Certain ARIA roles must be contained by particular parents (20 elements)
Certain ARIA roles must be contained by particular parents: 20 elements on the page fail this check, rated critical by axe-core.
6 buttons without a name
6 buttons have no accessible name, so screen readers announce just “button”.
Certain ARIA roles must contain particular children (3 elements)
Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
Unlabelled dropdowns
1 dropdown has no label.
ARIA dialog and alertdialog nodes should have an accessible name (32 elements)
ARIA dialog and alertdialog nodes should have an accessible name: 32 elements on the page fail this check, rated serious by axe-core.
15 text elements with low contrast
15 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.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (124 elements)
All page content should be contained by landmarks: 124 elements on the page fail this check, rated moderate by axe-core.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (1 element).
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (35 elements).
1 checks passed
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 69 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 15 failed. 7 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (77 characters)
Your title is 77 characters, so Google will cut it off around 60: “OMACUAN : Login Situs Toto Slot Online Gacor Terpercaya Gampang Menang Maxwin”.
2 H1 headlines
There are 2 <h1> headlines (“OMACUAN : Login Situs Toto Slot Online Gacor Terp…” and “OMACUAN: Login Situs Toto Slot Online Gacor Terpe…”). One clear main headline is easier for people and search engines.
25 links crawlers can't follow
25 links have no real href, so search engines can't follow them.
Meta description is long (163 characters)
Your meta description is 163 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
54 internal links, 67 external
The homepage links to 54 pages on afewwoodmen.com and 67 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://omacuanpintar.com/.
Structured data in place
Structured data found: BreadcrumbList, ItemList, OfferCatalog, Organization and Product.
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://omacuanpintar.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://omacuanpintar.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.
3 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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (3,261 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages point its canonical at the homepage
https://omacuanpintar.com/home, https://omacuanpintar.com/kebijakan-privasi, https://omacuanpintar.com/legal and https://omacuanpintar.com/sitemap 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.
5 pages share a title
/, https://omacuanpintar.com/home, https://omacuanpintar.com/kebijakan-privasi, https://omacuanpintar.com/legal and https://omacuanpintar.com/sitemap all use the title “OMACUAN : Login Situs Toto Slot Online Gacor Terpercaya Gampang Menan…”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages share a meta description
https://omacuanpintar.com/home, https://omacuanpintar.com/kebijakan-privasi, https://omacuanpintar.com/legal and https://omacuanpintar.com/sitemap use the same meta description. A description written for each page earns more clicks.
1 page slow to respond
https://omacuanpintar.com/sitemap took over 3 s to send its HTML from our server.
4 internal pages checked
We fetched 4 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 4 pages we checked loaded without an error.
Every page has a meta description
All 4 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 4 pages that loaded have a <title>.
Best practices
5 broken images
5 images failed to load on a phone, for example https://omacuanpintar.com/#.
53 small tap targets
53 of 70 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Unsafe attempt to load URL https://www.samsung.com/etc.clientlibs/samsung/clientlibs/consumer/global/clientlib-common/r…”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 1,824 words of copy
The homepage carries about 1,824 words of visible text.
5 checks passed
2 calls to action
The homepage has 2 calls to action, for example “OMACUAN Explore Shop” and “Shop”.
9 short forms
9 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 70 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Pinterest Tag (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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
26 other companies contacted
Loading the homepage contacts 26 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 afewwoodmen.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
- Hosting
- Cloudflare
Company
- Headquarters
- Atlanta
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 63 issues on afewwoodmen.com, including 25 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.