Website review, no card needed
norseprojects.com website review
Visit site (opens in a new tab)Reviewed 22 October 202620 issues · 70 checks
This review found 20 issues worth fixing on norseprojects.com, 7 of them high impact, across 70 checks. The most urgent: page weight: 7.0 MB in 155 requests. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 941 ms |
| May 9, 2026 | 930 ms |
| May 16, 2026 | 929 ms |
| May 23, 2026 | 896 ms |
| May 30, 2026 | 895 ms |
| Jun 6, 2026 | 915 ms |
| Jun 13, 2026 | 941 ms |
| Jun 20, 2026 | 971 ms |
| Jun 27, 2026 | 984 ms |
| Jul 4, 2026 | 933 ms |
| Jul 11, 2026 | 868 ms |
| Jul 18, 2026 | 893 ms |
| Jul 25, 2026 | 853 ms |
| Aug 1, 2026 | 835 ms |
| Aug 8, 2026 | 842 ms |
| Aug 15, 2026 | 792 ms |
| Aug 22, 2026 | 804 ms |
| Aug 29, 2026 | 840 ms |
| Sep 5, 2026 | 842 ms |
| Sep 12, 2026 | 875 ms |
| Sep 19, 2026 | 853 ms |
| Sep 26, 2026 | 806 ms |
| Oct 3, 2026 | 775 ms |
| Oct 10, 2026 | 725 ms |
| Oct 17, 2026 | 713 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 78 ms |
| May 9, 2026 | 76 ms |
| May 16, 2026 | 76 ms |
| May 23, 2026 | 74 ms |
| May 30, 2026 | 73 ms |
| Jun 6, 2026 | 74 ms |
| Jun 13, 2026 | 76 ms |
| Jun 20, 2026 | 77 ms |
| Jun 27, 2026 | 78 ms |
| Jul 4, 2026 | 78 ms |
| Jul 11, 2026 | 77 ms |
| Jul 18, 2026 | 78 ms |
| Jul 25, 2026 | 78 ms |
| Aug 1, 2026 | 78 ms |
| Aug 8, 2026 | 78 ms |
| Aug 15, 2026 | 77 ms |
| Aug 22, 2026 | 77 ms |
| Aug 29, 2026 | 77 ms |
| Sep 5, 2026 | 78 ms |
| Sep 12, 2026 | 79 ms |
| Sep 19, 2026 | 79 ms |
| Sep 26, 2026 | 79 ms |
| Oct 3, 2026 | 78 ms |
| Oct 10, 2026 | 79 ms |
| Oct 17, 2026 | 79 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
Legacy JavaScript
250 ms · 18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
Reduce unused CSS
150 ms · 44 KiBAbout 44 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused JavaScript
150 ms · 35 KiBAbout 35 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 8 KiB4 files are served with short cache lifetimes, so returning visitors download them again (8 KiB).
Render-blocking requests
150 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
3 third-party services on the page
3 third-party services load with your homepage (Klaviyo, Shopify and shop.app), adding 260 KiB and 73 ms of main-thread time.
Improve image delivery
36 KiB2 images could be 36 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 302 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.4 s
7.4 sYour largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Fall 26 Campaign — Documented in Gilleleje Havn”.
Time to Interactive: 7.4 s
7.4 sThe page becomes fully interactive after 7.4 s. Good is under 3.8 s.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 78 ms to 79 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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: 1.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 96 ms
96 msReal visitors wait 96 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: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 413 ms
413 msReal visitors wait 413 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 7.0 MB in 155 requests
7.0 MBYour homepage downloads 7.0 MB in 155 requests on a phone: media 5.5 MB (2), other files 747 KiB (82) and scripts 466 KiB (57). Under 2 MB keeps phones on slow connections fast.
About 2.0 g of CO₂ per visit
2.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.00 g of CO₂e: 239.7 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
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
47 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: 47 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (14 characters)
Your title is only 14 characters: “Norse Projects”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (197 characters)
Your meta description is 197 characters; Google truncates after about 160, so the end of your pitch is cut.
95 internal links, 3 external
The homepage links to 95 pages on norseprojects.com and 3 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Norse Projects”.
Canonical URL set
The canonical URL is https://norseprojects.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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://norseprojects.com/sitemap.xml.
AI search readiness
4 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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (502 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://norseprojects.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://norseprojects.com/collections/trousers and https://norseprojects.com/collections/sweatshirts, which answer with an error. Visitors hit a dead end and search engines drop them.
4 pages without a meta description
https://norseprojects.com/pages/collection-list, https://norseprojects.com/pages/accessories, https://norseprojects.com/collections/all and https://norseprojects.com/pages/brand have no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://norseprojects.com/collections/new-arrivals, https://norseprojects.com/pages/categories, https://norseprojects.com/pages/collection-list, https://norseprojects.com/collections/knitwear, https://norseprojects.com/collections/shirting and https://norseprojects.com/collections/t-shirts and 7 others 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 40 found) and read each the way a search engine does.
4 checks passed
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.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
8 small tap targets
8 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 286 words of copy
The homepage carries about 286 words of visible text.
2 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Shop”, “Shop All” and “Subscribe”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
14 other companies contacted
Loading the homepage contacts 14 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 norseprojects.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
Company
- Founded
- 2004
- Headquarters
- Copenhagen
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 20 issues on norseprojects.com, including 3 speed issues, 2 SEO issues and 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.