Website review, no card needed
cerestag.com website review
Visit site (opens in a new tab)Reviewed 7 November 202647 issues · 88 checks
This review found 47 issues worth fixing on cerestag.com, 15 of them high impact, across 88 checks. The most urgent: google Tag Manager adds 1.0 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
76C- #67,002 of 109,350 reviewed websitesbeats 34%
- #42,978 of 61,859 online storesbeats 26%
- #40,774 of 56,401 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 4.2 s |
| Sep 26, 2026 | 4.4 s |
| Oct 3, 2026 | 4.3 s |
| Oct 10, 2026 | 4.0 s |
| Oct 17, 2026 | 3.8 s |
| Oct 24, 2026 | 4.0 s |
| Oct 31, 2026 | 4.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 154 ms |
| May 23, 2026 | 135 ms |
| May 30, 2026 | 137 ms |
| Jun 6, 2026 | 140 ms |
| Jun 13, 2026 | 141 ms |
| Jun 20, 2026 | 137 ms |
| Jun 27, 2026 | 137 ms |
| Jul 4, 2026 | 137 ms |
| Jul 11, 2026 | 139 ms |
| Jul 18, 2026 | 146 ms |
| Jul 25, 2026 | 181 ms |
| Aug 1, 2026 | 197 ms |
| Aug 8, 2026 | 197 ms |
| Aug 15, 2026 | 224 ms |
| Aug 22, 2026 | 194 ms |
| Aug 29, 2026 | 197 ms |
| Sep 5, 2026 | 239 ms |
| Sep 12, 2026 | 222 ms |
| Sep 19, 2026 | 292 ms |
| Sep 26, 2026 | 327 ms |
| Oct 3, 2026 | 324 ms |
| Oct 10, 2026 | 318 ms |
| Oct 17, 2026 | 297 ms |
| Oct 24, 2026 | 285 ms |
| Oct 31, 2026 | 329 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
Speed
Google Tag Manager adds 1.0 s
1.0 sGoogle Tag Manager costs a phone 1.0 s of main-thread work and 1.0 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.
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Render-blocking requests
1.1 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
2.4 MB25 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Hubspot and others), adding 1.8 MB and 1.7 s of main-thread time.
Use efficient cache lifetimes
150 ms · 895 KiB88 files are served with short cache lifetimes, so returning visitors download them again (895 KiB).
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
652 KiBAbout 652 KiB of JavaScript is downloaded but never used on this page.
Facebook adds 403 ms
403 msFacebook costs a phone 403 ms of main-thread work and 308 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 319 ms. During a long task the page ignores taps.
Hubspot adds 232 ms
232 msHubspot costs a phone 232 ms of main-thread work and 324 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.
Reduce unused CSS
42 KiBAbout 42 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
26 KiBPolyfills for old browsers add 26 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.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Time to Interactive: 17.9 s
17.9 sThe page becomes fully interactive after 17.9 s. Good is under 3.8 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Speed Index: 7.6 s
7.6 sVisually, the page fills in at 7.6 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.7 s
3.7 sReal visitors wait 3.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 273 ms
273 msReal visitors wait 273 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 112% slower for real visitors
+112%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 154 ms to 329 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 53% slower for real visitors
+53%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.8 s to 4.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
54 images without width and height
54 images have no width and height attributes, so the layout jumps as each one loads.
4 checks passed
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
First Contentful Paint: 1.0 s
1.0 sThe first text or image appears after 1.0 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 1.0 s
1.0 sYour largest element renders in 1.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Our mission is that we believe change needs to happen to en…”.
Images and page weight
Page weight: 4.9 MB in 137 requests
4.9 MBYour homepage downloads 4.9 MB in 137 requests on a phone: images 2.9 MB (67), scripts 1.7 MB (30) and fonts 139 KiB (8). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
animal-health-features.jpg weighs 610 KiB. On a phone connection a single image that size takes seconds.
4 images far larger than shown
425 KiB4 images are downloaded at several times the size a phone draws them, for example animal-health-features.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 425 KiB.
2 images below the first screen load straight away
2 images further down the page (668 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.40 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.40 g of CO₂e: 167.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
Orphan list items
Some list items are not inside a list.
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.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings skip levels
Headings skip levels (h2 → h5, h1 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 62 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
25 H1 headlines
There are 25 <h1> headlines (“Continuous Improvement”, “Collaboration” and “Digital by Default”). One clear main headline is easier for people and search engines.
Meta description is long (163 characters)
Your meta description is 163 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links with vague text
2 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.
29 internal links, 27 external
The homepage links to 29 pages on cerestag.com and 27 external pages.
4 checks passed
Title: 64 characters
Your title is a healthy 64 characters: “GPS Tracking Device for Animals | Livestock Ear Tags | CERES TAG”.
Canonical URL set
The canonical URL is https://cerestag.com/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://cerestag.com/sitemap.xml.
AI search readiness
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://cerestag.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.
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 (798 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://cerestag.com/en/blogs/news has no <title>, so Google invents the link text in results.
5 pages without a meta description
https://cerestag.com/ceres-gen6, https://cerestag.com/impact, https://cerestag.com/en/blogs/news, https://cerestag.com/privacy-policy and https://cerestag.com/cookie-notice have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://cerestag.com/ceres-gen6, https://cerestag.com/ceres-rancher, https://cerestag.com/impact, https://cerestag.com/find-ceres-tag, https://cerestag.com/software-partners and https://cerestag.com/support and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://cerestag.com/find-ceres-tag 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://cerestag.com/software-partners, https://cerestag.com/support, https://cerestag.com/about-us, https://cerestag.com/en/blogs/news, https://cerestag.com/cookie-notice and https://cerestag.com/ccpa-opt-out 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 18 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.
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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
52 of 55 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 891 words of copy
The homepage carries about 891 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: “WHERE TO BUY”.
5 calls to action
The homepage has 5 calls to action, for example “Where to Buy”, “Learn More” and “Contact Us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 25 testimonial or review blocks, 18 customer or partner logos and 5 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and HubSpot.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 1 more (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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 8 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.
26 other companies contacted
Loading the homepage contacts 26 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 cerestag.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
- E-commerce
- 10 Shopify Products;Shopify;Shopify Plus
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Cloudflare
Company
- Headquarters
- Brisbane
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on cerestag.com, including 23 speed issues, 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.