Website review, no card needed

flangapp.com logo

flangapp.com website review

Visit site (opens in a new tab)Reviewed 7 November 202619 issues · 65 checks

This review found 19 issues worth fixing on flangapp.com, 6 of them high impact, across 65 checks. The most urgent: main-thread work: 5.2 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of flangapp.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. flangapp.com at 0.7 s0.7 s
  2. flangapp.com at 1.3 s1.3 s
  3. flangapp.com at 2.0 s2.0 s
  4. flangapp.com at 2.6 s2.6 s
  5. flangapp.com at 3.3 s3.3 s
  6. flangapp.com at 3.9 s3.9 s
  7. flangapp.com at 4.6 s4.6 s
  8. flangapp.com at 5.3 s5.3 s

Speed

4 to fix93
  • Main-thread work: 5.2 s

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

  • Improve image delivery

    1.1 MB

    8 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Render-blocking requests

    750 ms

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

  • rsms.me adds 1 ms

    1 ms

    rsms.me costs a phone 1 ms of main-thread work and 347 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.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Yandex Metrica, rsms.me and Impact Radius), adding 420 KiB and 62 ms of main-thread time.

  • Use efficient cache lifetimes

    58 KiB

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

  • Reduce unused JavaScript

    39 KiB

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

  • 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
  • Mobile performance score: 93

    93/100

    Your mobile performance score is 93. That is in Google's “good” band (90 and up).

  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

2 to fix92
  • Cumulative Layout Shift: 0.144

    0.144

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

  • 3 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

5 checks passed
  • First Contentful Paint: 1.6 s

    1.6 s

    The first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 1.6 s

    1.6 s

    Your largest element renders in 1.6 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Flangapp AI is a self-hosted platform you install on your o…”.

  • Speed Index: 2.1 s

    2.1 s

    Visually, the page fills in at 2.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

  • Time to Interactive: 1.6 s

    1.6 s

    The page is fully interactive after 1.6 s.

Images and page weight

5 to fix33
  • 1 image over 500 KB

    media_screen.png weighs 635 KiB. On a phone connection a single image that size takes seconds.

  • 10 images far larger than shown

    745 KiB

    10 images are downloaded at several times the size a phone draws them, for example media_screen.png at 792 px wide, shown at 240 px. Resized copies would save about 745 KiB.

  • Page weight: 2.7 MB in 44 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 44 requests on a phone: images 2.3 MB (30), fonts 345 KiB (1) and scripts 72 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 11 images in older formats

    11 images (2.1 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 10 images below the first screen load straight away

    10 images further down the page (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.8 g of CO₂ per visit

    0.76 g

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

Accessibility

2 to fixGoogle 9396
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements (1 element)

    <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 1 element on the page fails this check, rated serious by axe-core.

2 checks passed
  • Every image has alt text

    All 39 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10091
  • Meta description is long (162 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization and SoftwareApplication) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.

  • 31 internal links, 1 external

    The homepage links to 31 pages on flangapp.com and 1 external page.

6 checks passed
  • One H1 headline

    Your main headline reads: “Start your own AI app-building business”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Start Your Own AI App-Building Business | Flangapp AI”.

  • Canonical URL set

    The canonical URL is https://flangapp.com/.

  • 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://flangapp.com/sitemap.xml.

AI search readiness

100
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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (763 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes /llms.txt (8 KiB, 31 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix98
  • 3 pages share a meta description

    /docs/terms_of_service, /docs/policy and /docs/refund use the same meta description. A description written for each page earns more clicks.

  • 10 internal pages checked

    We fetched 10 pages linked from your homepage and read each the way a search engine does.

7 checks passed
  • Linked pages load

    All 10 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 10 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    5 of 5 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 738 words of copy

    The homepage carries about 738 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Buy license” and “Watch demo”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Buy license”, “Watch demo” and “Contact us”.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 4 other companies contacted

    Loading the homepage contacts 4 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 flangapp.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Hosting
Timeweb, LLP

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 19 issues on flangapp.com, including 6 speed issues, 2 SEO issues and 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25