Website review, no card needed

tempoinstitute.com logo

tempoinstitute.com website review

Visit site (opens in a new tab)Reviewed 23 October 202639 issues · 82 checks

This review found 39 issues worth fixing on tempoinstitute.com, 16 of them high impact, across 82 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.2 s2.0 sMay 2Oct 172.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.6 s
May 9, 20264.7 s
May 16, 20264.8 s
May 23, 20264.8 s
May 30, 20264.7 s
Jun 6, 20264.3 s
Jun 13, 20264.2 s
Jun 20, 20264.2 s
Jun 27, 20264.1 s
Jul 4, 20263.9 s
Jul 11, 20263.8 s
Jul 18, 20263.7 s
Jul 25, 20263.3 s
Aug 1, 20262.9 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.3 s
Oct 3, 20262.4 s
Oct 10, 20262.5 s
Oct 17, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
234 ms193 msMay 2Oct 17222 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026199 ms
May 9, 2026210 ms
May 16, 2026219 ms
May 23, 2026229 ms
May 30, 2026225 ms
Jun 6, 2026218 ms
Jun 13, 2026214 ms
Jun 20, 2026209 ms
Jun 27, 2026210 ms
Jul 4, 2026204 ms
Jul 11, 2026204 ms
Jul 18, 2026203 ms
Jul 25, 2026198 ms
Aug 1, 2026201 ms
Aug 8, 2026202 ms
Aug 15, 2026202 ms
Aug 22, 2026207 ms
Aug 29, 2026211 ms
Sep 5, 2026220 ms
Sep 12, 2026221 ms
Sep 19, 2026221 ms
Sep 26, 2026228 ms
Oct 3, 2026226 ms
Oct 10, 2026221 ms
Oct 17, 2026222 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 tempoinstitute.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tempoinstitute.com at 0.7 s0.7 s
  2. tempoinstitute.com at 1.4 s1.4 s
  3. tempoinstitute.com at 2.1 s2.1 s
  4. tempoinstitute.com at 2.8 s2.8 s
  5. tempoinstitute.com at 3.4 s3.4 s
  6. tempoinstitute.com at 4.1 s4.1 s
  7. tempoinstitute.com at 4.8 s4.8 s
  8. tempoinstitute.com at 5.5 s5.5 s

Speed

8 to fix63
  • Use efficient cache lifetimes

    2.5 s · 1.3 MB

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

  • Improve image delivery

    1.9 s · 620 KiB

    7 images could be 620 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.

  • Render-blocking requests

    1.2 s

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

  • Reduce unused JavaScript

    900 ms · 361 KiB

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

  • Mobile performance score: 63

    63/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and jQuery CDN and others), adding 1.1 MB and 745 ms of main-thread time.

  • Google Tag Manager adds 370 ms

    370 ms

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

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    12 KiB

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

  • 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 checks passed
  • Main-thread work: 1.7 s

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

  • Server response: 94 ms

    94 ms

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

Core Web Vitals

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

  • Real-user FCP: 3.4 s

    3.4 s

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

  • Largest Contentful Paint: 10.9 s

    10.9 s

    Your largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Teknik Menulis untuk Pemula”.

  • Time to Interactive: 12.6 s

    12.6 s

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

  • Real-user LCP: 3.5 s

    3.5 s

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

  • Real-user INP: 236 ms

    236 ms

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

  • Total Blocking Time: 382 ms

    382 ms

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

  • Speed Index: 4.2 s

    4.2 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 1 image without width and height

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

  • 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 199 ms to 222 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

  • Real-user TTFB: 733 ms

    733 ms

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

  • Largest content (LCP) got 45% faster for real visitors

    -45%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix69
  • Page weight: 2.4 MB in 69 requests

    2.4 MB

    Your homepage downloads 2.4 MB in 69 requests on a phone: images 1.3 MB (21), scripts 1.1 MB (16) and other files 21 KiB (27). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Kelas Online Teknik Menulis Untuk Pemula, Moerat Sitompul, T is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 5 images far larger than shown

    435 KiB

    5 images are downloaded at several times the size a phone draws them, for example bg-quote-first.webp at 2,880 px wide, shown at 390 px. Resized copies would save about 435 KiB.

  • 4 images in older formats

    4 images (455 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.7 g of CO₂ per visit

    0.68 g

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

Accessibility

9 to fixGoogle 7784
  • 6 buttons without a name

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

  • 7 text elements with low contrast

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

  • Links must have discernible text (2 elements)

    Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 8 images without alt text

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

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

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 39 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 10 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 (75 characters)

    Your title is 75 characters, so Google will cut it off around 60: “Tempo Institute - Belajar, Berlatih dan Pengembangan Diri Bersama Para Ahli”.

  • No social preview image

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

  • No X (Twitter) card tag

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

  • 79 internal links, 12 external

    The homepage links to 79 pages on tempoinstitute.com and 12 external pages.

6 checks passed
  • Meta description: 135 characters

    Your meta description is 135 characters: “Tempo Institute - Sekolah Jurnalistik Terbaik/ Kursus Jurnalistik Terbaik/ Tempat Pelatihan Menulis Terbaik untuk menam…”.

  • One H1 headline

    Your main headline reads: “Tempo Institute - Belajar, Berlatih dan Pengembangan Diri Bersama Para Ahli”.

  • Canonical URL set

    The canonical URL is https://tempoinstitute.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://tempoinstitute.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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 (1,334 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix81
  • 1 page points its canonical at the homepage

    https://tempoinstitute.com/course/detail/mini-class-menulis-buku-tanpa-buntu declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 8 pages share a title

    /, https://tempoinstitute.com/daftar-kelas, https://tempoinstitute.com/kelas-intensif/menulis-opini-ala-tempo, https://tempoinstitute.com/kelas-intensif/crafting-impactful-policy-briefs, https://tempoinstitute.com/course/detail/mini-class-menulis-buku-tanpa-buntu and https://tempoinstitute.com/kelas-intensif/public-speaking-presentasi-yang-powerful and 2 others all use the title “Tempo Institute - Belajar, Berlatih dan Pengembangan Diri Bersama Par…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages share a meta description

    https://tempoinstitute.com/daftar-kelas, https://tempoinstitute.com/kelas-intensif/menulis-opini-ala-tempo, https://tempoinstitute.com/kelas-intensif/crafting-impactful-policy-briefs, https://tempoinstitute.com/course/detail/mini-class-menulis-buku-tanpa-buntu, https://tempoinstitute.com/kelas-intensif/public-speaking-presentasi-yang-powerful and https://tempoinstitute.com/kelas-korporasi and 1 other use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 28 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).

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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 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 1,184 words of copy

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

2 checks passed
  • Social proof on the page

    Social proof on the homepage: 15 testimonial or review blocks, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 2 mores (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.

  • 11 cookies set on arrival

    11

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

  • 24 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager | Microsoft Clarity

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on tempoinstitute.com, including 18 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

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