Website review, no card needed

monark-cat.com logo

monark-cat.com website review

Visit site (opens in a new tab)Reviewed 26 October 202653 issues · 93 checks

This review found 53 issues worth fixing on monark-cat.com, 22 of them high impact, across 93 checks. The most urgent: reduce unused JavaScript. 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
8.4 s5.6 sMay 9Oct 247.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20265.9 s
May 16, 20266.0 s
May 23, 20266.4 s
May 30, 20266.8 s
Jun 6, 20266.9 s
Jun 13, 20266.8 s
Jun 20, 20266.5 s
Jun 27, 20266.4 s
Jul 4, 20266.5 s
Jul 11, 20266.7 s
Jul 18, 20266.7 s
Jul 25, 20266.7 s
Aug 1, 20266.7 s
Aug 8, 20266.8 s
Aug 15, 20266.9 s
Aug 22, 20266.9 s
Aug 29, 20266.9 s
Sep 5, 20267.2 s
Sep 12, 20267.7 s
Sep 19, 20267.7 s
Sep 26, 20268.0 s
Oct 3, 20267.8 s
Oct 10, 20267.9 s
Oct 17, 20267.8 s
Oct 24, 20267.2 s
Real-visitor tap response (INP)75th percentile, phones
405 ms152 msMay 9Oct 24346 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026201 ms
May 16, 2026181 ms
May 23, 2026207 ms
May 30, 2026239 ms
Jun 6, 2026244 ms
Jun 13, 2026258 ms
Jun 20, 2026243 ms
Jun 27, 2026275 ms
Jul 4, 2026294 ms
Jul 11, 2026295 ms
Jul 18, 2026294 ms
Jul 25, 2026264 ms
Aug 1, 2026264 ms
Aug 8, 2026260 ms
Aug 15, 2026285 ms
Aug 22, 2026278 ms
Aug 29, 2026278 ms
Sep 5, 2026285 ms
Sep 12, 2026255 ms
Sep 19, 2026273 ms
Sep 26, 2026324 ms
Oct 3, 2026339 ms
Oct 10, 2026376 ms
Oct 17, 2026376 ms
Oct 24, 2026346 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 monark-cat.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. monark-cat.com at 0.9 s0.9 s
  2. monark-cat.com at 1.9 s1.9 s
  3. monark-cat.com at 2.8 s2.8 s
  4. monark-cat.com at 3.7 s3.7 s
  5. monark-cat.com at 4.6 s4.6 s
  6. monark-cat.com at 5.6 s5.6 s
  7. monark-cat.com at 6.5 s6.5 s
  8. monark-cat.com at 7.4 s7.4 s

Speed

10 to fix36
  • Reduce unused JavaScript

    20.9 s · 3.8 MB

    About 3.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 20.9 s faster on a phone.

  • Improve image delivery

    8.8 s · 4.7 MB

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

  • YouTube adds 1.9 s

    1.9 s

    YouTube costs a phone 1.9 s of main-thread work and 7.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    1.9 s

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

  • Use efficient cache lifetimes

    1.4 s · 478 KiB

    19 files are served with short cache lifetimes, so returning visitors download them again (478 KiB).

  • Mobile performance score: 36

    36/100

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

  • Main-thread work: 8.0 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and Google CDN and others), adding 9.1 MB and 3.2 s of main-thread time.

  • Google Tag Manager adds 484 ms

    484 ms

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

  • Google CDN adds 388 ms

    388 ms

    Google CDN costs a phone 388 ms of main-thread work and 734 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

    200 ms · 43 KiB

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

  • 20 long tasks on the main thread

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

  • Font display

    150 ms

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

  • Reduce unused CSS

    131 KiB

    About 131 KiB of CSS is downloaded but never applied on this page.

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 84 ms

    84 ms

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

Core Web Vitals

14 to fix0
  • 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 LCP: 4.3 s

    4.3 s

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

  • Real-user CLS: 0.99

    0.99

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

  • Real-user FCP: 3.6 s

    3.6 s

    Real visitors see the first content after 3.6 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.

  • First Contentful Paint: 34.1 s

    34.1 s

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

  • Largest Contentful Paint: 61.7 s

    61.7 s

    Your largest element takes 61.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “…”.

  • Speed Index: 34.1 s

    34.1 s

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

  • Time to Interactive: 84.5 s

    84.5 s

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

  • Total Blocking Time: 803 ms

    803 ms

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

  • Real-user INP: 313 ms

    313 ms

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

  • Tap response (INP) got 89% slower for real visitors

    +89%

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

  • Largest content (LCP) got 27% slower for real visitors

    +27%

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

  • 1 image without width and height

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

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 17.2 MB in 249 requests

    17.2 MB

    Your homepage downloads 17.2 MB in 249 requests on a phone: scripts 8.2 MB (87), images 6.0 MB (39) and fonts 1.2 MB (18). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Monark-Bukidnon-84.jpg weighs 1.6 MB. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    1.8 MB

    4 images are downloaded at several times the size a phone draws them, for example Monark-Bukidnon-84.jpg at 2,048 px wide, shown at 149 px. Resized copies would save about 1.8 MB.

  • 10 images in older formats

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

  • 7 images below the first screen load straight away

    7 images further down the page (349 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.9 g of CO₂ per visit

    4.87 g

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

Accessibility

8 to fixGoogle 8592
  • 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.

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 4 form fields without a label

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

  • 4 links without text

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

  • ARIA role should be appropriate for the element (4 elements)

    ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (4 elements)

    Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 29 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 7772
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (26 characters)

    Your title is only 26 characters: “Home - Monark - Cat Dealer”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 4 H1 headlines

    There are 4 <h1> headlines (“Deals & Promotion”, “Blog” and “We'd love to help you with your requirements”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 7 links with vague text

    7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 6 links crawlers can't follow

    6 links have no real href, so search engines can't follow them.

  • 116 internal links, 10 external

    The homepage links to 116 pages on monark-cat.com and 10 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://monark-cat.com/.

  • Structured data in place

    Structured data found: Organization, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://monark-cat.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

Other pages

3 to fix86
  • 1 linked page hidden from search

    https://monark-cat.com/product-category/power-systems/engineering-capabilities is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 7 pages without a meta description

    https://monark-cat.com/product-category/power-systems/electric-power/diesel-generator-sets, https://monark-cat.com/product-category/power-systems/electric-power/diesel-generator-sets/rental, https://monark-cat.com/product-category/power-systems/electric-power/gas-generator-sets, https://monark-cat.com/product-category/power-systems/marine, https://monark-cat.com/product-category/power-systems/hybrid and https://monark-cat.com/product-category/power-systems/engineering-capabilities and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://monark-cat.com/power-systems, https://monark-cat.com/parts-step-by-steps and https://monark-cat.com/used-parts-for-cat-generator-sets use the same meta description. A description written for each page earns more clicks.

  • 11 pages slow to respond

    https://monark-cat.com/new-equipments, https://monark-cat.com/partner-brands/allied, https://monark-cat.com/power-systems, https://monark-cat.com/product-category/power-systems/electric-power/diesel-generator-sets, https://monark-cat.com/product-category/power-systems/electric-power/diesel-generator-sets/rental and https://monark-cat.com/product-category/power-systems/electric-power/gas-generator-sets and 5 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 50 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 6588
  • 15 small tap targets

    15 of 59 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 14 distorted images

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

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 fix86
  • Thin social proof

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

  • A 9-field form

    Your longest form asks for 9 fields (0 required). Every extra field lowers completion.

  • About 1,021 words of copy

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

5 checks passed
  • Clear next step on the first screen

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

  • 11 calls to action

    The homepage has 11 calls to action, for example “Contact Us”, “Request a Quote” and “Learn More”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies, 1 of them by other companies (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.

  • 28 other companies contacted

    Loading the homepage contacts 28 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 monark-cat.com, 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
E-commerce
WooCommerce
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 53 issues on monark-cat.com, including 24 speed issues, 6 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