Website review, no card needed
rodanurmala.com website review
Visit site (opens in a new tab)Reviewed 18 October 202629 issues · 79 checks
This review found 29 issues worth fixing on rodanurmala.com, 9 of them high impact, across 79 checks. The most urgent: avoid multiple page redirects. 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 895 ms |
| May 2, 2026 | 833 ms |
| May 9, 2026 | 909 ms |
| May 16, 2026 | 871 ms |
| May 23, 2026 | 923 ms |
| May 30, 2026 | 846 ms |
| Jun 6, 2026 | 847 ms |
| Jun 13, 2026 | 839 ms |
| Aug 22, 2026 | 566 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.7 s
2.2 s
2.6 s
3.0 s
3.5 s
Speed
Avoid multiple page redirects
6.2 sThe page goes through 1 redirect before it starts loading, costing about 6.2 s. Link and advertise the final URL directly.
Render-blocking requests
1.1 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 42
42/100Your mobile performance score is 42 (desktop: 88). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 742 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
270 ms · 46 KiBAbout 46 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 270 ms faster on a phone.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 134 ms. During a long task the page ignores taps.
Phones get a much slower page than desktops
Desktop scores 88 but mobile only 42. A gap that wide usually means heavy scripts and images that hit phones hardest.
Use efficient cache lifetimes
6 KiB4 files are served with short cache lifetimes, so returning visitors download them again (6 KiB).
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.
Improve image delivery
5 KiB1 image could be 5 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
1 third-party service on the page
1 third-party service load with your homepage (JSDelivr CDN), adding 25 KiB and 0 ms of main-thread time.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.2 s
10.2 sYour largest element takes 10.2 s to render on a phone. Google's threshold for “good” is 2.5 s.
Cumulative Layout Shift: 0.481
0.481The layout shifts by 0.481 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 10.3 s
10.3 sThe page becomes fully interactive after 10.3 s. Good is under 3.8 s.
Speed Index: 5.1 s
5.1 sVisually, the page fills in at 5.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Total Blocking Time: 289 ms
289 msScripts block taps and scrolling for 289 ms in total while the page loads. Good is under 200 ms.
17 images without width and height
17 images have no width and height attributes, so the layout jumps as each one loads.
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.
1 checks passed
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
1 image below the first screen load straight away
1 image further down the page (72 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.4 g of CO₂ per visit
0.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.39 g of CO₂e: 47.3 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.4 MB in 162 requests
1.4 MBYour homepage downloads 1.4 MB in 162 requests on a phone: images 724 KiB (81), fonts 342 KiB (20) and scripts 287 KiB (30). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
All page content should be contained by landmarks (25 elements)
All page content should be contained by landmarks: 25 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails 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.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
23 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 29 WCAG 2.2 A/AA and best-practice rules on the phone render: 23 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (23 characters)
Your title is only 23 characters: “POMPA PEMADAM KEBAKARAN”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
44 internal links, 6 external
The homepage links to 44 pages on rodanurmala.com and 6 external pages.
6 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “PT. Roda Nurmala adalah perusahaan penyedia produk dan jasa POMPA PEMADAM KEBAKARAN. Selain itu kami juga menyediakan p…”.
One H1 headline
Your main headline reads: “POMPA PEMADAM KEBAKARAN”.
Canonical URL set
The canonical URL is https://www.rodanurmala.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.
XML sitemap found
Your XML sitemap is reachable at https://www.rodanurmala.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.rodanurmala.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,507 words), so crawlers that don't run JavaScript still read it.
Other pages
8 pages without a meta description
https://www.rodanurmala.com/Services.htm, https://www.rodanurmala.com/Projects-References.htm, https://www.rodanurmala.com/News.htm, https://www.rodanurmala.com/Page/contact-us.html, https://www.rodanurmala.com/Products/Fire-Pump/Horizontal-Split-Case.html and https://www.rodanurmala.com/Products/Fire-Pump/End-Suction.html and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://www.rodanurmala.com/Services.htm, https://www.rodanurmala.com/Projects-References.htm and https://www.rodanurmala.com/News.htm have no <h1> headline, so visitors and search engines get no clear main topic.
11 pages with very little text
https://www.rodanurmala.com/Products.htm, https://www.rodanurmala.com/Services.htm, https://www.rodanurmala.com/Page/contact-us.html, https://www.rodanurmala.com/Products/Fire-Pump/Horizontal-Split-Case.html, https://www.rodanurmala.com/Products/Fire-Pump/End-Suction.html and https://www.rodanurmala.com/Products/Plumbing-Pump-/Vertical-Multi-Stage.html and 5 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
No mobile viewport
No viewport meta tag, so phones render the desktop layout zoomed out.
7 third-party cookies
7 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 (Forbidden)”.
4 low-resolution images
4 images are served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Tap targets are thumb-sized
11 of 13 tappable elements near the top are at least 24 px.
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.
Local business without LocalBusiness data
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 1,402 words of copy
The homepage carries about 1,402 words of visible text.
5 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact Us”.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and 1 trust badge.
Direct contact links
Visitors can reach you directly: 3 phone links and 2 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
10 cookies set on arrival
10Opening the homepage sets 10 cookies (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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 rodanurmala.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2024.
Stack
- Framework
- jQuery
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on rodanurmala.com, including 11 speed issues, 2 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.