simpleflying.com website review

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.7 s faster on a phone.

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

Your mobile performance score is 42 (desktop: 58). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (adsninja.ca, Pubmatic and simpleflyingimages.com and others), adding 2.4 MB and 1.4 s of main-thread time.

10 images could be 266 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

adsninja.ca costs a phone 361 ms of main-thread work and 505 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.

simpleflyingimages.com costs a phone 183 ms of main-thread work and 862 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.

Other Google APIs/SDKs costs a phone 183 ms of main-thread work and 493 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.

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

Polyfills for old browsers add 80 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

14 KiB could be saved by minifying JavaScript.

About 62 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.

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

Your largest element takes 28.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Robots Cut An F-35”.

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

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

Scripts block taps and scrolling for 538 ms in total while the page loads. Good is under 200 ms.

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

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

Over the last 25 four-week periods to 2026-10-03, 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.4 MB in 1,286 requests on a phone: scripts 2.5 MB (105), HTML 656 KiB (208) and images 577 KiB (381). Under 2 MB keeps phones on slow connections fast.

the-airline-that-created-premium-economy-now-has-the-most-sp 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).

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

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

37 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

10 tap targets are too small or too close together to hit reliably with a finger.

2 links inside paragraphs rely on colour alone to stand out.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

5 visible links have no text or label, so screen readers cannot say where they go.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your meta description is only 60 characters: “The leading independent voice for aviation news and insight.”. 70 to 160 characters is enough to sell the click.

6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 274 pages on simpleflying.com and 32 external pages.

Your robots.txt shuts out ChatGPT (ChatGPT-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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 /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.

robots.txt blocks GPTBot, ClaudeBot, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

/feed has no <title>, so Google invents the link text in results.

/feed has no meta description, so Google writes the search snippet from whatever text it finds.

/threads, /flight-tracker, /videos, /page/newsletter and /feed have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) Error: Unable to find element with ID: comments-feed-list.”.

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.

Social proof on the homepage: “2K Users”. 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.

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

Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Google Ads, Google Analytics and Google Tag Manager 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.

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