Website review, no card needed

krost.com.au logo

krost.com.au website review

Visit site (opens in a new tab)Reviewed 21 October 202633 issues · 85 checks

This review found 33 issues worth fixing on krost.com.au, 9 of them high impact, across 85 checks. The most urgent: render-blocking requests. 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.3 s1.2 sJun 6Oct 171.7 s
Show as table
DateReal-visitor load time (LCP)
Jun 6, 20261.3 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.6 s
Jul 11, 20261.8 s
Jul 18, 20262.0 s
Jul 25, 20262.2 s
Aug 1, 20262.1 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20261.8 s
Aug 29, 20261.6 s
Sep 5, 20261.5 s
Sep 12, 20261.4 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.6 s
Oct 17, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
80 ms63 msJun 6Oct 1771 ms
Show as table
DateReal-visitor tap response (INP)
Jun 6, 202666 ms
Jun 13, 202670 ms
Jun 20, 202665 ms
Jun 27, 202668 ms
Jul 4, 202670 ms
Jul 11, 202667 ms
Jul 18, 202670 ms
Jul 25, 202671 ms
Aug 1, 202678 ms
Aug 8, 202676 ms
Aug 15, 202674 ms
Aug 22, 202671 ms
Aug 29, 202671 ms
Sep 5, 202671 ms
Sep 12, 202670 ms
Sep 19, 202670 ms
Sep 26, 202671 ms
Oct 3, 202670 ms
Oct 10, 202670 ms
Oct 17, 202671 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 krost.com.au (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. krost.com.au at 0.5 s0.5 s
  2. krost.com.au at 1.0 s1.0 s
  3. krost.com.au at 1.5 s1.5 s
  4. krost.com.au at 1.9 s1.9 s
  5. krost.com.au at 2.4 s2.4 s
  6. krost.com.au at 2.9 s2.9 s
  7. krost.com.au at 3.4 s3.4 s
  8. krost.com.au at 3.9 s3.9 s

Speed

7 to fix63
  • Render-blocking requests

    2.0 s

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

  • Improve image delivery

    450 ms · 1.6 MB

    26 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Reduce unused JavaScript

    900 ms · 193 KiB

    About 193 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 (desktop: 79). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    900 ms · 96 KiB

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

  • Google Tag Manager adds 350 ms

    350 ms

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

  • 5 long tasks on the main thread

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and openai.com and others), adding 495 KiB and 427 ms of main-thread time.

  • Minify JavaScript

    150 ms · 33 KiB

    33 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    150 ms · 22 KiB

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

  • Legacy JavaScript

    150 ms · 8 KiB

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

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.4 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

8 to fix100
  • 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: 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 text “Built to Inspire Curate a space that fuels productivity, su…”.

  • Time to Interactive: 22.7 s

    22.7 s

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

  • Speed Index: 6.3 s

    6.3 s

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

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

    +25%

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

  • Real-user TTFB: 984 ms

    984 ms

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

  • Total Blocking Time: 290 ms

    290 ms

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

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

6 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 64 ms

    64 ms

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

  • Real-user CLS: 0.06

    0.06

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.009

    0.009

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

Images and page weight

3 to fix50
  • Page weight: 5.4 MB in 124 requests

    5.4 MB

    Your homepage downloads 5.4 MB in 124 requests on a phone: images 2.5 MB (34), fonts 1.9 MB (10) and scripts 822 KiB (59). Under 2 MB keeps phones on slow connections fast.

  • 14 images in older formats

    14 images (1.9 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 far larger than shown

    403 KiB

    7 images are downloaded at several times the size a phone draws them, for example Design_resources_textiles.jpg at 800 px wide, shown at 169 px. Resized copies would save about 403 KiB.

  • About 1.5 g of CO₂ per visit

    1.53 g

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

1 checks passed
  • Images load when needed

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

Accessibility

5 to fixGoogle 8591
  • ARIA roles used must conform to valid values (1 element)

    ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • ARIA commands must have an accessible name (11 elements)

    ARIA commands must have an accessible name: 11 elements on the page fail this check, rated serious by axe-core.

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

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 36 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 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

4 to fixGoogle 8587
  • 2 H1 headlines

    There are 2 <h1> headlines (“Built to Inspire” and “Featured Products Discover our curated range of p…”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected non-whitespace character after JSON at position 2)”.

  • 5 links with vague text

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 194 internal links, 8 external

    The homepage links to 194 pages on krost.com.au and 8 external pages.

6 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Australian commercial furniture specialist since 1989. Workstations, seating, desks, storage and joinery, with showroom…”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Commercial Office Furniture Australia | Krost”.

  • Canonical URL set

    The canonical URL is https://krost.com.au/.

  • 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://krost.com.au/sitemap.xml.

AI search readiness

1 to fix88
  • 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://krost.com.au/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,096 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://krost.com.au/resources, whose canonical is https://krost.com.au/resources/models. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://krost.com.au/resources has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

1 to fixGoogle 9693
  • 18 small tap targets

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

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

1 to fix94
  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 803 words of copy

    The homepage carries about 803 words of visible text.

7 checks passed
  • Clear next step on the first screen

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

  • 13 calls to action

    The homepage has 13 calls to action, for example “Contact Us”, “Sign Up” and “Shop Now”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 9 cookies set on arrival

    9

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

  • 10 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Vue.js
Analytics
Google Analytics | Google Tag Manager
Hosting
Amazon

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on krost.com.au, including 15 speed issues, 4 SEO issues and 1 conversion gap. 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