pigax.com website review

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

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

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

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

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

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

33 KiB could be saved by minifying CSS.

3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 233 KiB and 98 ms of main-thread time.

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

1 long task block the main thread while loading, the longest for 63 ms. During a long task the page ignores taps.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 9.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The only Piggery Farm Manager App you Need! Increase the Ef…”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

pigs-in-pen.png weighs 500 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 2.0 MB in 47 requests on a phone: images 1.4 MB (12), scripts 274 KiB (17) and stylesheets 199 KiB (13). Under 2 MB keeps phones on slow connections fast.

8 images (1.3 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.

5 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example hero-26-img.png at 1,500 px wide, shown at 366 px. Resized copies would save about 42 KiB.

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

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

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 on the page fails this check, rated moderate by axe-core.

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

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

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

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

There is no robots.txt at pigax.com/robots.txt, the first file search crawlers ask for.

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

The homepage links to 15 pages on pigax.com and 5 external pages.

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.

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

https://pigax.com/en and / all use the title “Pigax.com - Your No 1 Free Piggery Management System”. Search engines can't tell which page to show for a search, so each competes with the others.

/, https://pigax.com/en/Tour, https://pigax.com/en/Blog, https://pigax.com/en/Faq, https://pigax.com/en/Documentation and https://pigax.com/en/Contact and 3 others use the same meta description. A description written for each page earns more clicks.

/, https://pigax.com/en/Tour, https://pigax.com/en/Blog, https://pigax.com/en/Faq, https://pigax.com/en/Documentation and https://pigax.com/en/Contact and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://pigax.com/en/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.

We fetched 9 pages linked from your homepage and read each the way a search engine does.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 295 words of visible text.

Before a visitor clicks anything, the page loads 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.

Opening the homepage sets 2 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.