Website review, no card needed
riassociates.com website review
Visit site (opens in a new tab)Reviewed 21 October 202637 issues · 74 checks
This review found 37 issues worth fixing on riassociates.com, 15 of them high impact, across 74 checks. The most urgent: improve image delivery. 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
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.2 s |
| May 9, 2026 | 3.0 s |
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 235 ms |
| May 9, 2026 | 212 ms |
| May 16, 2026 | 200 ms |
| May 23, 2026 | 193 ms |
| May 30, 2026 | 193 ms |
| Jun 6, 2026 | 219 ms |
| Jun 13, 2026 | 227 ms |
| Jun 20, 2026 | 213 ms |
| Jun 27, 2026 | 219 ms |
| Jul 4, 2026 | 205 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.4 s
0.9 s
1.3 s
1.8 s
2.2 s
2.7 s
3.1 s
3.5 s
Speed
Improve image delivery
3.0 s · 645 KiB3 images could be 645 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.
Use efficient cache lifetimes
2.4 s · 573 KiB7 files are served with short cache lifetimes, so returning visitors download them again (573 KiB).
Mobile performance score: 75
75/100Your mobile performance score is 75 (desktop: 83). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
600 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Reduce unused CSS
300 ms · 70 KiBAbout 70 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (envato-static.com, Pinterest and Cloudflare and others), adding 1.1 MB and 83 ms of main-thread time.
b-cdn.net adds 0 ms
0 msb-cdn.net costs a phone 0 ms of main-thread work and 723 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.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 57 ms. During a long task the page ignores taps.
Reduce unused JavaScript
28 KiBAbout 28 KiB of JavaScript is downloaded but never used on this page.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need.
Minify CSS
9 KiB9 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.
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 128 ms of it running JavaScript. That is comfortably low.
Server response: 180 ms
180 msYour server sent the HTML in 180 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.3 s
6.3 sYour largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SULETOTO menghadirkan panduan upload aplikasi resmi Slot On…”.
Time to Interactive: 6.4 s
6.4 sThe page becomes fully interactive after 6.4 s. Good is under 3.8 s.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 235 ms to 205 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.2 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Not enough real-visitor data yet
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.
3 checks passed
Speed Index: 2.4 s
2.4 sVisually, the page fills in at 2.4 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0.01
0.01The layout barely moves while loading (CLS 0.01, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
1 image over 500 KB
suletoto-9.jpg weighs 514 KiB. On a phone connection a single image that size takes seconds.
2 images in older formats
2 images (668 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.
About 0.3 g of CO₂ per visit
0.31 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.31 g of CO₂e: 37.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.1 MB in 25 requests
1.1 MBYour homepage downloads 1.1 MB in 25 requests on a phone: images 864 KiB (8), scripts 95 KiB (8) and stylesheets 79 KiB (4). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
<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 (39 elements)
All page content should be contained by landmarks: 39 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
robots.txt blocks all crawlers
Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “SULETOTO : Panduan Upload Aplikasi Resmi Slot Online Tergacor Hari Ini”.
2 H1 headlines
There are 2 <h1> headlines (“SULETOTO : Panduan Upload Aplikasi Resmi Slot Onl…” and “SULETOTO > Panduan Upload Aplikasi Resmi dengan A…”). One clear main headline is easier for people and search engines.
Meta description is long (233 characters)
Your meta description is 233 characters; Google truncates after about 160, so the end of your pitch is cut.
168 internal links, 55 external
The homepage links to 168 pages on riassociates.com and 55 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.nautiseltzer.com/nauti_news.html.
Structured data in place
Structured data found: BreadcrumbList, Organization and Product.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
XML sitemap found
Your XML sitemap is reachable at https://www.nautiseltzer.com/sitemap.xml.
AI search readiness
robots.txt blocks 6 AI answer engine crawlers
6 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
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.
3 checks passed
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,232 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.nautiseltzer.com/llms.txt (1 KiB, 0 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
4 linked pages are broken
Your homepage links to https://www.nautiseltzer.com/nauti_news.htmllicenses/standard, https://www.nautiseltzer.com/item_support/what_is_item_support/8988002, https://www.nautiseltzer.com/nauti_news.htmlhc/en-us/articles/41383541904281-Envato-Market-Terms and https://www.nautiseltzer.com/nauti_news.htmllicenses, which answer with an error. Visitors hit a dead end and search engines drop them.
4 internal pages checked
We fetched 4 pages linked from your homepage and read each the way a search engine does.
Best practices
8 small tap targets
8 of 20 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.”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “$ is not defined”.
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
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 832 words of copy
The homepage carries about 832 words of visible text.
3 checks passed
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 54 testimonial or review blocks, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Microsoft Ads and Pinterest Tag (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 riassociates.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on riassociates.com, including 11 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.