Website review, no card needed
sealandgov.org website review
Visit site (opens in a new tab)Reviewed 6 November 202632 issues · 88 checks
This review found 32 issues worth fixing on sealandgov.org, 11 of them high impact, across 88 checks. The most urgent: youTube adds 1.1 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
81B- #41,468 of 124,235 reviewed websitesbeats 61%
- #27,465 of 69,818 online storesbeats 54%
- #26,461 of 63,496 Shopify storesbeats 52%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 144 ms |
| May 23, 2026 | 148 ms |
| May 30, 2026 | 149 ms |
| Jun 6, 2026 | 149 ms |
| Jun 13, 2026 | 151 ms |
| Jun 20, 2026 | 151 ms |
| Jun 27, 2026 | 150 ms |
| Jul 4, 2026 | 151 ms |
| Jul 11, 2026 | 149 ms |
| Jul 18, 2026 | 143 ms |
| Jul 25, 2026 | 141 ms |
| Aug 1, 2026 | 142 ms |
| Aug 8, 2026 | 142 ms |
| Aug 15, 2026 | 144 ms |
| Aug 22, 2026 | 145 ms |
| Aug 29, 2026 | 144 ms |
| Sep 5, 2026 | 143 ms |
| Sep 12, 2026 | 145 ms |
| Sep 19, 2026 | 152 ms |
| Sep 26, 2026 | 161 ms |
| Oct 3, 2026 | 164 ms |
| Oct 10, 2026 | 170 ms |
| Oct 17, 2026 | 172 ms |
| Oct 24, 2026 | 169 ms |
| Oct 31, 2026 | 170 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
YouTube adds 1.1 s
1.1 sYouTube costs a phone 1.1 s of main-thread work and 1.9 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.
Mobile performance score: 43
43/100Your mobile performance score is 43. 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, 3.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
750 ms · 2.5 MBAbout 2.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and Shopify and others), adding 4.3 MB and 2.4 s of main-thread time.
Use efficient cache lifetimes
600 ms · 452 KiB21 files are served with short cache lifetimes, so returning visitors download them again (452 KiB).
Render-blocking requests
800 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
Google Tag Manager adds 505 ms
505 msGoogle Tag Manager costs a phone 505 ms of main-thread work and 667 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.
Shopify adds 320 ms
320 msShopify costs a phone 320 ms of main-thread work and 1.2 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.
2,836 HTML elements
The page has 2,836 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
pop-convert.com adds 261 ms
261 mspop-convert.com costs a phone 261 ms of main-thread work and 162 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 221 ms. During a long task the page ignores taps.
Reduce unused CSS
135 KiBAbout 135 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
100 ms · 32 KiBPolyfills for old browsers add 32 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Improve image delivery
47 KiB2 images could be 47 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
8 KiB8 KiB could be saved by minifying JavaScript.
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: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.7 s
9.7 sYour largest element takes 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 39.1 s
39.1 sThe page becomes fully interactive after 39.1 s. Good is under 3.8 s.
Speed Index: 11.8 s
11.8 sVisually, the page fills in at 11.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 982 ms
982 msScripts block taps and scrolling for 982 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 144 ms to 170 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-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 139 ms
139 msReal visitors wait 139 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 740 ms
740 msReal visitors wait 740 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.027
0.027The layout barely moves while loading (CLS 0.027, good is under 0.1).
Images and page weight
Page weight: 6.8 MB in 357 requests
6.8 MBYour homepage downloads 6.8 MB in 357 requests on a phone: scripts 4.2 MB (90), other files 1.2 MB (158) and fonts 572 KiB (16). Under 2 MB keeps phones on slow connections fast.
About 1.9 g of CO₂ per visit
1.93 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.93 g of CO₂e: 231.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
25 text elements with low contrast
25 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
18 links without text
18 visible links have no text or label, so screen readers cannot say where they go.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 19 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “Sealand Official | Principality Of Sealand – Principality of Sealand”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
41 internal links, 21 external
The homepage links to 41 pages on sealandgov.org and 21 external pages.
6 checks passed
Meta description: 132 characters
Your meta description is 132 characters: “Nobility titles | Join our adventure and become a Lord, Lady or Noble Knight | Principality Of Sealand: The world's Sma…”.
One H1 headline
Your main headline reads: “Principality of Sealand”.
Canonical URL set
The canonical URL is https://sealandgov.org/en-us.
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://sealandgov.org/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://sealandgov.org/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 (715 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without an H1
https://sealandgov.org/en-us/products/become-a-baron-or-baroness and https://sealandgov.org/en-us/products/becoming-a-knight have 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 21 found) and read each the way a search engine does.
6 checks passed
Linked pages load
3 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 3 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 3 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 24 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.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
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
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 433 words of copy
The homepage carries about 433 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: “Learn more” and “[email protected]”.
10 calls to action
The homepage has 10 calls to action, for example “[email protected]”, “JOIN US” and “JOIN OUR DISCORD”.
3 short forms
3 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and X (Twitter) Ads (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
15Opening the homepage sets 15 cookies, 4 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.
46 other companies contacted
Loading the homepage contacts 46 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 sealandgov.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 22 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Gsc Instagram Feed · Flash Search Filter Search · Ecomposer Builder · The4 Toolkit · Fontify · Ryviu Product Reviews · Instafeed · Gdpr Cookie Consent · Sales Shield · Ecodrive Dashboard · Forms · Checkout Rules · Ecomsend · cloudfront.net · avada.io · digital-downloads.com · printful.com · pop-convert.com · sealandgov.org · goaffpro.com · wetracked.io
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Shopify
Company
- Founded
- 1967
- Headquarters
- Southend-on-Sea
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on sealandgov.org, including 16 speed issues, 2 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.