runningoffthereeses.com website review

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

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

8 third-party services load with your homepage (sprinklr.com, Adobe Tag Manager and Facebook and others), adding 1.9 MB and 1.6 s of main-thread time.

55 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

About 1.1 MB of JavaScript is downloaded but never used on this page.

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

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

sprinklr.com costs a phone 284 ms of main-thread work and 425 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.

Adobe Tag Manager costs a phone 283 ms of main-thread work and 149 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.

Facebook costs a phone 261 ms of main-thread work and 255 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 Maps costs a phone 200 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.

Google CDN costs a phone 143 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.

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

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

Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need.

7 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

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

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

Your largest element takes 3.7 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.4 s).

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.

Your homepage downloads 2.6 MB in 162 requests on a phone: scripts 2.2 MB (80), images 148 KiB (14) and HTML 89 KiB (7). Under 2 MB keeps phones on slow connections fast.

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

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

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

Certain ARIA roles must be contained by particular parents: 18 elements on the page fail this check, rated critical by axe-core.

6 buttons have no accessible name, so screen readers announce just “button”.

Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

1 dropdown has no label.

ARIA dialog and alertdialog nodes should have an accessible name: 32 elements on the page fail this check, rated serious by axe-core.

Some list items are not inside a list.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

Elements use prohibited ARIA attributes (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 on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (33 elements).

Your title is 74 characters, so Google will cut it off around 60: “PINTUTOGEL: Pusat Situs Togel Online Pasaran Lengkap Paling Bergengsi 2026”.

There are 2 <h1> headlines (“PINTUTOGEL: Pusat Situs Togel Online Pasaran Leng…” and “PINTUTOGEL: Pusat Situs Togel Online Pasaran Leng…”). One clear main headline is easier for people and search engines.

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

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

Structured data found (BreadcrumbList, FAQPage, OfferCatalog and Organization) but with 1 problem, for example “Organization: url points at a different host (https://example.com/)”.

No XML sitemap at https://www.runningoffthereeses.com/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 76 pages on runningoffthereeses.com and 66 external pages.

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

Your homepage links to https://www.runningoffthereeses.com/kebijakan-privasi, https://www.runningoffthereeses.com/legal and https://www.runningoffthereeses.com/sitemap, which answer with an error. Visitors hit a dead end and search engines drop them.

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

5 images failed to load on a phone, for example https://www.runningoffthereeses.com/#.

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

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 is set on load; browsers are restricting these, so whatever relies on them breaks.

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…”.

Chrome logged issues while loading the page (“Cookie”).

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 1,777 words of visible text.

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

Opening the homepage sets 13 cookies (measured from a US location before any click).

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.

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