craftmakerscollective.com website review

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

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

8 third-party services load with your homepage (YouTube, piwik.pro and cookieinformation.com and others), adding 16.7 MB and 631 ms of main-thread time.

unibrew.com costs a phone 0 ms of main-thread work and 15.5 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.

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

YouTube costs a phone 530 ms of main-thread work and 1,009 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.

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

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

The page has 1,513 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

15 files block the first paint until they finish downloading. Deferring or inlining them could save about 250 ms.

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

About 87 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 22 KiB JavaScript that modern phones do not need.

Your largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (5.2 s).

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 135 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 17.3 MB in 97 requests on a phone: media 14.2 MB (8), scripts 1.4 MB (34) and images 1.3 MB (19). Under 2 MB keeps phones on slow connections fast.

smukfest_2023_recap_v200_00_28_15still003.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

3 images are downloaded at several times the size a phone draws them, for example 20180827_oly00180_1.jpg at 2,880 px wide, shown at 390 px. Resized copies would save about 399 KiB.

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

11 buttons have no accessible name, so screen readers announce just “button”.

Certain ARIA roles must contain particular children: 4 elements on the page fail this check, rated critical by axe-core.

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

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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 visible links have no text or label, so screen readers cannot say where they go.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Elements with visible text labels do not have matching accessible names. (3 elements).

Your title is only 13 characters: “Royal Unibrew”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 12 <h1> headlines (“Royal Unibrew og Tivoli forlænger partnerskab”, “46 år sammen: Smukfest og Royal Unibrew fortsætte…” and “Faxe Kondi og Uno-X Mobility Cycling indgår partn…”). One clear main headline is easier for people and search engines.

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

Your meta description is 276 characters; Google truncates after about 160, so the end of your pitch is cut.

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

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

The homepage links to 51 pages on craftmakerscollective.com and 18 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://royalunibrew.dk/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://royalunibrew.dk/nyheder/pressekontakt has no meta description, so Google writes the search snippet from whatever text it finds.

https://royalunibrew.dk/karriere, https://royalunibrew.dk/karriere/karriere-i-royal-unibrew and https://royalunibrew.dk/karriere/internationale-karrieremuligheder use the same meta description. A description written for each page earns more clicks.

https://royalunibrew.dk/brands, https://royalunibrew.dk/brands/oel, https://royalunibrew.dk/brands/laeskedrikke, https://royalunibrew.dk/brands/rtd-cider-cocktails, https://royalunibrew.dk/brands/energi-funktionelle-drikke and https://royalunibrew.dk/brands/egekilde and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 26 found) and read each the way a search engine does.

2 images failed to load on a phone, for example https://www.royalunibrew.com/wp-content/uploads/2018/09/RoyalUnibrew_logo.png.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 880 words of visible text.

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

Opening the homepage sets 1 cookie, 1 of them by other companies (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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.