ikytai.com website review

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

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

About 810 KiB of CSS is downloaded but never applied on this page.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Adobe Tag Manager and others), adding 954 KiB and 712 ms of main-thread time.

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

3 images could be 291 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

Reduce initial server response time. Google estimates savings of 562 ms on a phone.

The HTML itself could arrive about 550 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Google Tag Manager costs a phone 348 ms of main-thread work and 434 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.

Your server takes 662 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

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

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

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

Your largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “DEWALANGIT77: Situs Slot Gacor Terpercaya Dengan Winrate Te…”.

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

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

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

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

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.2 MB in 37 requests on a phone: scripts 977 KiB (24), HTML 884 KiB (1) and images 372 KiB (5). Under 2 MB keeps phones on slow connections fast.

1 image (142 KiB) 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.

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

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

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

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

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

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 75 characters, so Google will cut it off around 60: “DEWALANGIT77: Situs Slot Gacor Terpercaya Dengan Winrate Tertinggi Saat Ini”.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

A phone browser shows 1,152 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

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.

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

3 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot set properties of undefined (setting 'execStart')”.

No character set is declared, so some characters can render as gibberish.

1 image is served at too low a resolution for sharp phone screens.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Hotjar, LinkedIn Insight and Meta Pixel and 1 more (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 3 cookies, 1 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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.