Website review, no card needed

thedudesthreads.com logo

thedudesthreads.com website review

Visit site (opens in a new tab)Reviewed 9 November 202638 issues · 75 checks

This review found 38 issues worth fixing on thedudesthreads.com, 13 of them high impact, across 75 checks. The most urgent: improve image delivery. 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
7.7 s1.8 sOct 3Nov 72.5 s
Show as table
DateReal-visitor load time (LCP)
Oct 3, 20267.0 s
Oct 10, 20266.4 s
Oct 17, 20263.1 s
Oct 24, 20262.6 s
Oct 31, 20262.5 s
Nov 7, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
406 ms339 msOct 3Nov 7347 ms
Show as table
DateReal-visitor tap response (INP)
Oct 3, 2026361 ms
Oct 10, 2026398 ms
Oct 17, 2026359 ms
Oct 24, 2026351 ms
Oct 31, 2026347 ms
Nov 7, 2026347 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 thedudesthreads.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thedudesthreads.com at 0.6 s0.6 s
  2. thedudesthreads.com at 1.2 s1.2 s
  3. thedudesthreads.com at 1.8 s1.8 s
  4. thedudesthreads.com at 2.4 s2.4 s
  5. thedudesthreads.com at 3.0 s3.0 s
  6. thedudesthreads.com at 3.6 s3.6 s
  7. thedudesthreads.com at 4.2 s4.2 s
  8. thedudesthreads.com at 4.8 s4.8 s

Speed

7 to fix53
  • Improve image delivery

    2.1 s · 529 KiB

    10 images could be 529 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

  • Use efficient cache lifetimes

    2.1 s · 471 KiB

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 53

    53/100

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

  • Reduce unused CSS

    450 ms · 72 KiB

    About 72 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • 7 third-party services on the page

    7 third-party services load with your homepage (envato-static.com, Cloudflare and Bing Ads and others), adding 1.0 MB and 86 ms of main-thread time.

  • kilat.digital adds 0 ms

    0 ms

    kilat.digital costs a phone 0 ms of main-thread work and 570 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.

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

  • Minify CSS

    8 KiB

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

2 checks passed
  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 136 ms of it running JavaScript. That is comfortably low.

  • Server response: 220 ms

    220 ms

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

Core Web Vitals

9 to fix67
  • 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.

  • Largest Contentful Paint: 6.4 s

    6.4 s

    Your largest element takes 6.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “COLOKSGP 𝗓ᶻ Signature Situs Togel Online Terpercaya | Agen…”.

  • Cumulative Layout Shift: 0.453

    0.453

    The layout shifts by 0.453 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Real-user INP: 347 ms

    347 ms

    Real visitors wait 347 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 2.1 s

    2.1 s

    Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

  • Time to Interactive: 6.5 s

    6.5 s

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

  • Speed Index: 4.5 s

    4.5 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -9%

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

5 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

    Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 463 ms

    463 ms

    Real visitors wait 463 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 63% faster for real visitors

    -63%

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

2 to fix80
  • 3 images in older formats

    3 images (635 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.

  • 2 images far larger than shown

    103 KiB

    2 images are downloaded at several times the size a phone draws them, for example c48a93ed90eaf0bafa5d39212fa0eeeb.jpg at 1,080 px wide, shown at 326 px. Resized copies would save about 103 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (288 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.3 g of CO₂ per visit

    0.30 g

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

1 checks passed
  • Page weight: 1.1 MB in 34 requests

    1.1 MB

    Your homepage downloads 1.1 MB in 34 requests on a phone: images 889 KiB (20), stylesheets 77 KiB (3) and scripts 67 KiB (8). That is a lean page.

Accessibility

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

  • <svg> elements with an img or image role must have alternative text (1 element)

    <svg> elements with an img or image role must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • 3 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

1 checks passed
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 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

4 to fixGoogle 9279
  • Title is long (83 characters)

    Your title is 83 characters, so Google will cut it off around 60: “COLOKSGP 𝗓ᶻ Signature Situs Togel Online Terpercaya | Agen Togel Terbaik Masa Kini”.

  • 3 H1 headlines

    There are 3 <h1> headlines (“COLOKSGP 𝗓ᶻ Signature Situs Togel Online Terperc…”, “COLOKSGP 𝗓ᶻ Signature Situs Togel Online Terperc…” and “COLOKSGP 𝗓ᶻ Signature Situs Togel Online Terperc…”). One clear main headline is easier for people and search engines.

  • Meta description is long (314 characters)

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

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, FAQPage, Organization and Product) but with 1 problem, for example “Product: no offers (price) block”.

  • 149 internal links, 49 external

    The homepage links to 149 pages on thedudesthreads.com and 49 external pages.

4 checks passed
  • Canonical URL set

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

  • 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://adaptationpodcast.com/sitemap.xml.

AI search readiness

1 to fix85
  • Snippets are switched off

    The robots meta tag says “index, follow, nosnippet”, which tells Google, Bing and the AI answers built on them not to quote this page.

  • No llms.txt

    There is no https://adaptationpodcast.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

Other pages

1 to fix0
  • 2 linked pages are broken

    Your homepage links to //licenses/standard and https://adaptationpodcast.com/item_support/what_is_item_support/8988002, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 internal pages checked

    We fetched 2 pages linked from your homepage and read each the way a search engine does.

Best practices

3 to fixGoogle 9285
  • 7 small tap targets

    7 of 25 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 404 ()”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 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 909 words of copy

    The homepage carries about 909 words of visible text.

3 checks passed
  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 14 testimonial or review blocks, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Microsoft Ads (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.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie, 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.

  • 7 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Plus
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 thedudesthreads.com, including 16 speed issues, 4 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