Website review, no card needed

aag.co.id logo

aag.co.id website review

Visit site (opens in a new tab)Reviewed 24 October 202644 issues · 81 checks

This review found 44 issues worth fixing on aag.co.id, 17 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
5.7 s4.0 sMay 2Aug 84.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.3 s
May 9, 20265.0 s
May 16, 20265.3 s
May 23, 20265.4 s
May 30, 20265.5 s
Jun 6, 20265.1 s
Jun 13, 20265.1 s
Jun 20, 20264.6 s
Jun 27, 20264.4 s
Jul 4, 20264.2 s
Jul 11, 20264.2 s
Jul 18, 20264.3 s
Jul 25, 20264.5 s
Aug 1, 20264.5 s
Aug 8, 20264.3 s

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

Full-page screenshot of aag.co.id (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aag.co.id at 1.1 s1.1 s
  2. aag.co.id at 2.2 s2.2 s
  3. aag.co.id at 3.4 s3.4 s
  4. aag.co.id at 4.5 s4.5 s
  5. aag.co.id at 5.6 s5.6 s
  6. aag.co.id at 6.7 s6.7 s
  7. aag.co.id at 7.9 s7.9 s
  8. aag.co.id at 9.0 s9.0 s

Speed

12 to fix22
  • Use efficient cache lifetimes

    5.8 s · 2.5 MB

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

  • Improve image delivery

    6.3 s · 1.8 MB

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

  • Render-blocking requests

    2.1 s

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

  • Mobile performance score: 22

    22/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Hotjar and others), adding 1.3 MB and 1.8 s of main-thread time.

  • Google Tag Manager adds 886 ms

    886 ms

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

  • Reduce unused JavaScript

    150 ms · 717 KiB

    About 717 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Font display

    750 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 750 ms).

  • Reduce unused CSS

    600 ms · 73 KiB

    About 73 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • 15 long tasks on the main thread

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

  • Main-thread work: 3.7 s

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

  • Facebook adds 273 ms

    273 ms

    Facebook costs a phone 273 ms of main-thread work and 225 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.

  • Legacy JavaScript

    150 ms · 33 KiB

    Polyfills for old browsers add 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify CSS

    150 ms · 8 KiB

    8 KiB could be saved by minifying CSS.

  • Minify JavaScript

    11 KiB

    11 KiB could be saved by minifying JavaScript.

  • Phones get a much slower page than desktops

    Desktop scores 49 but mobile only 22. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

1 checks passed
  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix22
  • Largest Contentful Paint: 11.0 s

    11.0 s

    Your largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “First slide”.

  • Speed Index: 13.3 s

    13.3 s

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

  • Time to Interactive: 19.0 s

    19.0 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Cumulative Layout Shift: 0.286

    0.286

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

  • 17 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -4%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.3 s to 4.3 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.

Images and page weight

5 to fix18
  • Page weight: 4.8 MB in 105 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 105 requests on a phone: images 3.0 MB (26), scripts 1.4 MB (34) and fonts 214 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Website-AAG.jpeg weighs 1,000 KiB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    564 KiB

    2 images are downloaded at several times the size a phone draws them, for example Website-AAG.jpeg at 1,500 px wide, shown at 390 px. Resized copies would save about 564 KiB.

  • 17 images in older formats

    17 images (2.5 MB) 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.

  • 16 images below the first screen load straight away

    16 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.4 g of CO₂ per visit

    1.37 g

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

Accessibility

6 to fixGoogle 8390
  • 2 text elements with low contrast

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

  • 3 images without alt text

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

  • All page content should be contained by landmarks (7 elements)

    All page content should be contained by landmarks: 7 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.

  • 13 links without text

    13 visible links have no text or label, so screen readers cannot say where they go.

  • 5 form fields without a label

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

  • Headings skip levels

    Headings skip levels (h1 → h3, h2 → h6 and h2 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 36 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 6 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8587
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 3 H1 headlines

    There are 3 <h1> headlines (“Your Partner in Pest Management Solutions”, “The AAG Team” and “Serving You Better in”). One clear main headline is easier for people and search engines.

  • No robots.txt

    There is no robots.txt at aag.co.id/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 41 internal links, 8 external

    The homepage links to 41 pages on aag.co.id and 8 external pages.

5 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “AAG Pest Control Merupakan Jasa Pengendalian Hama Permukiman Indonesia, Memberikan Layanan Berkualitas untuk Mengendali…”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “Jasa Pengendalian Hama - AAG Pest Control”.

  • Canonical URL set

    The canonical URL is https://www.aag.co.id/.

  • 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.aag.co.id/sitemap.xml.

AI search readiness

1 to fix81
  • 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.aag.co.id/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.

1 checks passed
  • Text is in the HTML

    Your server sends the page's text in the HTML (248 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix79
  • 14 pages point its canonical at the homepage

    https://www.aag.co.id/introduction, https://www.aag.co.id/our-policies, https://www.aag.co.id/apps, https://www.aag.co.id/blog, https://www.aag.co.id/termite-control and https://www.aag.co.id/fumigation and 8 others declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 7 pages without a meta description

    https://www.aag.co.id/redirect, https://www.aag.co.id/apps, https://www.aag.co.id/id-home, https://www.aag.co.id/mosquito-control, https://www.aag.co.id/cockroach-control and https://www.aag.co.id/flies-control and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.aag.co.id/our-policies and https://www.aag.co.id/termite-control use the same meta description. A description written for each page earns more clicks.

  • 13 pages without an H1

    https://www.aag.co.id/redirect, https://www.aag.co.id/introduction, https://www.aag.co.id/our-policies, https://www.aag.co.id/blog, https://www.aag.co.id/termite-control and https://www.aag.co.id/fumigation and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.aag.co.id/insect-light-trap has 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 22 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9276
  • 1 broken image

    1 image failed to load on a phone, for example https://aag.co.id/storage/app/media/pest/nyamuk.gif.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    8 of 8 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 200 words

    The homepage has only about 200 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

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

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Us”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Hotjar, TikTok Pixel and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 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.

  • 25 other companies contacted

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

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 aag.co.id, 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
Analytics
Google Analytics | Google Tag Manager | Hotjar

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on aag.co.id, including 19 speed issues, 3 SEO issues and 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25