Website review, no card needed

nextdigital.co.id logo

nextdigital.co.id website review

Visit site (opens in a new tab)Reviewed 21 October 202627 issues · 71 checks

This review found 27 issues worth fixing on nextdigital.co.id, 8 of them high impact, across 71 checks. The most urgent: improve image delivery. 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
2.7 s2.4 sMay 2Oct 172.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.4 s
May 9, 20262.5 s
May 16, 20262.5 s
May 23, 20262.6 s
May 30, 20262.6 s
Jun 6, 20262.6 s
Jun 13, 20262.6 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.6 s
Aug 8, 20262.5 s
Aug 15, 20262.6 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
258 ms212 msMay 2Oct 17253 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026234 ms
May 9, 2026219 ms
May 16, 2026217 ms
May 23, 2026224 ms
May 30, 2026224 ms
Jun 6, 2026220 ms
Jun 13, 2026226 ms
Jun 20, 2026227 ms
Jun 27, 2026219 ms
Jul 4, 2026225 ms
Jul 11, 2026219 ms
Jul 18, 2026218 ms
Jul 25, 2026223 ms
Aug 1, 2026220 ms
Aug 8, 2026227 ms
Aug 15, 2026220 ms
Aug 22, 2026220 ms
Aug 29, 2026251 ms
Sep 5, 2026236 ms
Sep 12, 2026243 ms
Sep 19, 2026239 ms
Sep 26, 2026228 ms
Oct 3, 2026227 ms
Oct 10, 2026237 ms
Oct 17, 2026253 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

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

How it loaded on a phone

  1. nextdigital.co.id at 0.4 s0.4 s
  2. nextdigital.co.id at 0.8 s0.8 s
  3. nextdigital.co.id at 1.1 s1.1 s
  4. nextdigital.co.id at 1.5 s1.5 s
  5. nextdigital.co.id at 1.9 s1.9 s
  6. nextdigital.co.id at 2.3 s2.3 s
  7. nextdigital.co.id at 2.6 s2.6 s
  8. nextdigital.co.id at 3.0 s3.0 s

Speed

3 to fix65
  • Improve image delivery

    1.9 s · 346 KiB

    1 image could be 346 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

  • Mobile performance score: 65

    65/100

    Your mobile performance score is 65 (desktop: 74). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    600 ms · 170 KiB

    About 170 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.

  • 2 long tasks on the main thread

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

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Fonts and nextdev.id), adding 47 KiB and 0 ms of main-thread time.

2 checks passed
  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 75 ms of it running JavaScript. That is comfortably low.

  • Server response: 29 ms

    29 ms

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

Core Web Vitals

11 to fix33
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Largest Contentful Paint: 5.9 s

    5.9 s

    Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Next Digital Indonesia Creative Digital Marketing Agency Di…”.

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

  • Real-user LCP: 2.6 s

    2.6 s

    Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 253 ms

    253 ms

    Real visitors wait 253 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 2.4 s

    2.4 s

    Real visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.

  • 43 images without width and height

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

  • Time to Interactive: 5.9 s

    5.9 s

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

  • Cumulative Layout Shift: 0.148

    0.148

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

  • Speed Index: 3.5 s

    3.5 s

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

  • Tap response (INP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 234 ms to 253 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +6%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 checks passed
  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix90
  • 1 image far larger than shown

    340 KiB

    1 image is downloaded at several times the size a phone draws it, for example Untitled-design-7.png at 2,000 px wide, shown at 117 px. Resized copies would save about 340 KiB.

  • 1 image in older formats

    1 image (351 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.

  • About 0.3 g of CO₂ per visit

    0.28 g

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

2 checks passed
  • Page weight: 1,003 KiB in 35 requests

    1,003 KiB

    Your homepage downloads 1,003 KiB in 35 requests on a phone: images 571 KiB (7), stylesheets 194 KiB (22) and fonts 161 KiB (4). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

5 to fixGoogle 8490
  • 4 text elements with low contrast

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

  • 2 tap targets too small

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

  • 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 (23 elements)

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

1 checks passed
  • 37 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: 37 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9290
  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Next Digital - Digital Marketing Agency Jakarta | Advertising Agency”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 37 internal links, 2 external

    The homepage links to 37 pages on nextdigital.co.id and 2 external pages.

6 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “Kami Digital Agency yang menyediakan layanan digital marketing & digital advertising Jakarta untuk meningkatkan bisnis …”.

  • One H1 headline

    Your main headline reads: “Next Digital Indonesia Creative Digital Marketing Agency”.

  • Canonical URL set

    The canonical URL is https://nextdigital.co.id/.

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and WebPage.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://nextdigital.co.id/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

Other pages

3 to fix85
  • 2 pages without a meta description

    https://nextdigital.co.id/blog and https://nextdigital.co.id/contact have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://nextdigital.co.id/case_study, whose canonical is https://nextdigital.co.id/case-study. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://nextdigital.co.id/privacy-policy and https://nextdigital.co.id/contact have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://nextdigital.co.id/contact 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 20 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

Google 100100
2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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.

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

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

  • About 346 words of copy

    The homepage carries about 346 words of visible text.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 2 other companies contacted

    Loading the homepage contacts 2 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 nextdigital.co.id, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on nextdigital.co.id, including 14 speed issues, 2 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