rekmed.org website review

2 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.7 s faster on a phone.

About 1.2 MB 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.

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

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

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

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

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

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

Adobe Tag Manager costs a phone 265 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.

sprinklr.com costs a phone 217 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 Maps costs a phone 203 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 99 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.

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

Polyfills for old browsers add 31 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.

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

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

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

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

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

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

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

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.

logo-untung88.webp weighs 810 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.7 MB in 168 requests on a phone: scripts 2.3 MB (85), images 1.2 MB (14) and HTML 104 KiB (7). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example banner-untung88.webp at 1,254 px wide, shown at 350 px. Resized copies would save about 104 KiB.

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

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

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

3 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 83 characters, so Google will cut it off around 60: “UNTUNG88 : Website Permainan Online Dengan Rating Tertinggi Terpercaya di Indonesia”.

Your canonical URL points to sanduskyorthodontics.com, not rekmed.org, so Google may credit that host instead.

There are 2 <h1> headlines (“UNTUNG88 : Website Permainan Online Dengan Rating…” and “UNTUNG88 : Website Permainan Online Dengan Rating…”). 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 183 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (BreadcrumbList, ItemList, OfferCatalog and Organization) but with 2 problems, for example “Organization: url points at a different host (https://www.sanduskyorthodontics.com/)”.

No XML sitemap at https://rekmed.org/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to only 3 pages on your own site, so visitors and crawlers find few routes into the rest of it.

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

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.

/, https://rekmed.org/kebijakan-privasi, https://rekmed.org/legal and https://rekmed.org/sitemap all use the title “UNTUNG88 : Website Permainan Online Dengan Rating Tertinggi Terpercay…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://rekmed.org/kebijakan-privasi, https://rekmed.org/legal and https://rekmed.org/sitemap use the same meta description. A description written for each page earns more clicks.

https://rekmed.org/legal took over 3 s to send its HTML from our server.

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://rekmed.org/#.

44 of 59 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…”.

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

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,787 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 12 cookies, 2 of them by other companies (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 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.