Website review, no card needed

yancoal.com.au logo

yancoal.com.au website review

Visit site (opens in a new tab)Reviewed 25 October 202659 issues · 98 checks

This review found 59 issues worth fixing on yancoal.com.au, 19 of them high impact, across 98 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
3.3 s2.3 sMay 2Oct 172.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.8 s
May 9, 20262.7 s
May 16, 20262.7 s
May 23, 20262.8 s
May 30, 20262.8 s
Jun 6, 20262.9 s
Jun 13, 20263.1 s
Jun 20, 20263.1 s
Jun 27, 20263.2 s
Jul 4, 20263.0 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20263.0 s
Aug 8, 20262.9 s
Aug 15, 20262.8 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.6 s
Sep 26, 20262.5 s
Oct 3, 20262.6 s
Oct 10, 20262.9 s
Oct 17, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
130 ms78 msMay 2Oct 1799 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202696 ms
May 9, 202695 ms
May 16, 202696 ms
May 23, 202687 ms
May 30, 202691 ms
Jun 6, 2026104 ms
Jun 13, 2026118 ms
Jun 20, 2026124 ms
Jun 27, 2026121 ms
Jul 4, 2026111 ms
Jul 11, 2026104 ms
Jul 18, 2026101 ms
Jul 25, 202697 ms
Aug 1, 202692 ms
Aug 8, 202688 ms
Aug 15, 202687 ms
Aug 22, 202684 ms
Aug 29, 202690 ms
Sep 5, 202697 ms
Sep 12, 202698 ms
Sep 19, 2026105 ms
Sep 26, 2026103 ms
Oct 3, 202698 ms
Oct 10, 2026102 ms
Oct 17, 202699 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 yancoal.com.au (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. yancoal.com.au at 1.0 s1.0 s
  2. yancoal.com.au at 2.0 s2.0 s
  3. yancoal.com.au at 3.0 s3.0 s
  4. yancoal.com.au at 4.0 s4.0 s
  5. yancoal.com.au at 5.0 s5.0 s
  6. yancoal.com.au at 6.0 s6.0 s
  7. yancoal.com.au at 7.0 s7.0 s
  8. yancoal.com.au at 8.1 s8.1 s

Speed

12 to fix54
  • Render-blocking requests

    4.0 s

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

  • Reduce unused JavaScript

    3.0 s · 512 KiB

    About 512 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.

  • Improve image delivery

    150 ms · 6.7 MB

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

  • Mobile performance score: 54

    54/100

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Vimeo and jQuery CDN and others), adding 3.0 MB and 540 ms of main-thread time.

  • Use efficient cache lifetimes

    650 ms · 48 KiB

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

  • Document request latency

    650 ms

    The HTML itself could arrive about 650 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    630 ms

    Reduce initial server response time. Google estimates savings of 630 ms on a phone.

  • Vimeo adds 182 ms

    182 ms

    Vimeo costs a phone 182 ms of main-thread work and 2.6 MB 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 Tag Manager adds 322 ms

    322 ms

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

  • Main-thread work: 3.3 s

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

  • Server response: 730 ms

    730 ms

    Your server takes 730 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 9 long tasks on the main thread

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

  • Reduce unused CSS

    170 ms · 64 KiB

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

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

Core Web Vitals

10 to fix67
  • 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 TTFB: 1.9 s

    1.9 s

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

  • Largest Contentful Paint: 14.5 s

    14.5 s

    Your largest element takes 14.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Yancoal Australia Celebrating 20 years in Australia Learn a…”. Most of its time is resource load delay (5.9 s).

  • Speed Index: 15.6 s

    15.6 s

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

  • Time to Interactive: 20.9 s

    20.9 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Real-user LCP: 3.6 s

    3.6 s

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

  • Real-user FCP: 2.9 s

    2.9 s

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

  • Total Blocking Time: 268 ms

    268 ms

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

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +5%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 96 ms to 99 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.8 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user INP: 112 ms

    112 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

5 to fix18
  • Page weight: 25.6 MB in 123 requests

    25.6 MB

    Your homepage downloads 25.6 MB in 123 requests on a phone: media 14.6 MB (1), images 7.4 MB (16) and other files 2.1 MB (12). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 6.1 MB together. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    3.5 MB

    3 images are downloaded at several times the size a phone draws them, for example Rectangle-523-1.jpg at 1,605 px wide, shown at 350 px. Resized copies would save about 3.5 MB.

  • 7 images in older formats

    7 images (7.0 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.

  • 4 images below the first screen load straight away

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

  • About 7.3 g of CO₂ per visit

    7.26 g

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

Accessibility

12 to fixGoogle 8085
  • 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.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 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.

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 form fields without a label

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

  • 3 links without text

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

  • ARIA role should be appropriate for the element (1 element)

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

1 checks passed
  • 40 automated accessibility rules passed

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

SEO

7 to fixGoogle 7761
  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (21 characters)

    Your title is only 21 characters: “Yancoal – Coal Mining”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 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 XML sitemap

    No XML sitemap at https://www.yancoal.com.au/wp-sitemap.xml, so Google discovers your pages only by following links.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

  • 100 internal links, 3 external

    The homepage links to 100 pages on yancoal.com.au and 3 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://www.yancoal.com.au/.

  • robots.txt in place

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

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://www.yancoal.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,482 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix85
  • 15 pages without a meta description

    https://www.yancoal.com.au/suppliers, https://www.yancoal.com.au/contact-us, https://www.yancoal.com.au/zh/home, https://www.yancoal.com.au/about-us, https://www.yancoal.com.au/board and https://www.yancoal.com.au/executive-team and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.yancoal.com.au/board, whose canonical is https://www.yancoal.com.au/about-us/board. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 14 pages without an H1

    https://www.yancoal.com.au/suppliers, https://www.yancoal.com.au/contact-us, https://www.yancoal.com.au/zh/home, https://www.yancoal.com.au/about-us, https://www.yancoal.com.au/board and https://www.yancoal.com.au/executive-team and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.yancoal.com.au/zh/home 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.

  • 7 pages slow to respond

    https://www.yancoal.com.au/corporate-governance, https://www.yancoal.com.au/our-sites, https://www.yancoal.com.au/our-sites/moolarben, https://www.yancoal.com.au/our-sites/hunter-valley-operations, https://www.yancoal.com.au/our-sites/stratford and https://www.yancoal.com.au/our-sites/duralie and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 38 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 7385
  • 2 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Executing inline script violates the following Content Security Policy directive 'script-src 'self' 'nonce-fpJmP28epcMp…”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix56
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

    The homepage carries about 675 words of visible text.

3 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact us”, “Learn more” and “Get in touch”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 2 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.

  • 8 other companies contacted

    Loading the homepage contacts 8 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 yancoal.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

CMS
WordPress
Framework
jQuery
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 59 issues on yancoal.com.au, including 22 speed issues, 7 SEO issues and 5 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