flyingtiger.com website review

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

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

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

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

8 third-party services load with your homepage (Shopify, shgcdn3.com and Pinterest and others), adding 2.0 MB and 353 ms of main-thread time.

Shopify costs a phone 251 ms of main-thread work and 1.9 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.

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

25 KiB could be saved by minifying JavaScript.

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

10 files are served with short cache lifetimes, so returning visitors download them again (65 KiB).

About 59 KiB of JavaScript is downloaded but never used on this page.

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Christmas magic for every corner Find everything from tree …”.

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

The layout shifts by 0.269 while loading, so content jumps under the reader's thumb. Good is under 0.1.

For real visitors the layout shifts by 0.22 (75th percentile). Good is under 0.1.

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

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

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

Your homepage downloads 4.9 MB in 288 requests on a phone: images 2.6 MB (70), other files 951 KiB (114) and fonts 624 KiB (5). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example 905926fab1a2066146f74fcfce7383e0.jpg at 553 px wide, shown at 139 px. Resized copies would save about 46 KiB.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

6 images have no alt text, which hurts accessibility and image search.

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is only 23 characters: “Flying Tiger Copenhagen”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“Christmas magic for every corner” and “For everyone on your list”). One clear main headline is easier for people and search engines.

The homepage links to 510 pages on flyingtiger.com and 9 external pages.

Your homepage links to /pages/help, which answers with an error. Visitors hit a dead end and search engines drop it.

/, /collections/new-in, /collections/christmas, /collections/gifts-1, /collections/ski-village and /collections/nordic-christmas and 9 others all use the title “Flying Tiger Copenhagen”. Search engines can't tell which page to show for a search, so each competes with the others.

/collections/new-in, /collections/christmas, /collections/gifts-1, /collections/ski-village, /collections/nordic-christmas and /collections/mugs-ceramics-1 and 8 others use the same meta description. A description written for each page earns more clicks.

/collections/new-in, /collections/christmas, /collections/gifts-1, /collections/ski-village, /collections/nordic-christmas and /collections/mugs-ceramics-1 and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 link from your homepage to your own site is broken, for example https://flyingtiger.com/pages/help (404).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example http://www.findsmiley.dk/112291.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

flyingtiger.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

flyingtiger.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 1,037 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

DMARC is set to p=none, so mail pretending to be flyingtiger.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Klaviyo and Microsoft Clarity (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 8 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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.