Skip to content
Audit Complete

Results for https://fundable.com

Visit site
SaaS / Software Tracking: signups
Spain Spain · Madrid Completed: Apr 22, 2026 23:49 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
D67

Site Health

Score: 67 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Major barriers for users with disabilities — up to 15% of your audience.

Well-optimized for search — your content is discoverable.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Adobe Fonts · 229 peers
You 67
·
Avg 73
-6 below average
0 50 100
Amazon Route 53 · 975 peers
You 67
·
Avg 72
At average
0 50 100
Better than 1% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

Top Priorities (5)

1

/.svn/entries is publicly accessible

Security gaps expose your site and users to attacks, eroding trust.

Security › Information Leakage
2

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
3

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
4

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
5

Page weighs 16.5 MB (12.4 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

4

High impact, low effort — start here.

Strategic

1

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Ffundable.com)](https://beavercheck.com/results/aa5710fc-2577-4e86-afdf-72bc851ead9f)
<a href="https://beavercheck.com/results/aa5710fc-2577-4e86-afdf-72bc851ead9f"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ffundable.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Ffundable.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site has several issues that may be affecting user experience and business outcomes. Your LCP of 17.6s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. The 4 security gaps leave your users exposed — modern browsers increasingly warn visitors about insecure sites. Addressing the critical issues below would have the most immediate impact on your user trust.

4 security gaps detected — browsers may warn visitors about your site.
Your LCP is 17.6s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
C
Could reach Estimate based on resolving critical issues

Conversion Barriers

3 critical 9 warning

12 barrier(s) likely increasing bounce by ~36%.

Speed (2)

Page takes 17.6s to load

+12% bounce

Users abandon at ~3s — you're 15.1s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

High main-thread blocking time

+2% bounce

Page is non-interactive for 310ms after first paint

Fix: Defer third-party scripts and split large bundles

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (3)

Severe layout shift during page load

+6% bounce

Users mis-click when content jumps — converting intent into frustration

Fix: Reserve space for images, ads, and embeds with explicit width/height

1 form field(s) without a label

+2% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

Viewport disables user zoom

+2% bounce

Visitors with low vision can't read the page — and some jurisdictions treat this as a legal risk

Fix: Remove user-scalable=no; drop maximum-scale if it's below 2

Content (3)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (2)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

3 broken link(s) on the page

+5% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€340 investment → €2.88/month returns + EUR 120,500,000 risk avoided

Payback period: > 2 years First-year ROI: -90%

Investment

€340

4h · 5 findings

Monthly returns

€2.88 /mo

~€35 / year

  • Bandwidth savings €2.88

Regulatory risk avoided

EUR 120,500,000

if kept compliant

  • ePrivacy Directive EUR 100,000,000
  • GDPR EUR 20,000,000
  • EAA EUR 500,000

€170 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

€340

4.0 developer hours at €85/hr

Based on European Union rates (€85/hr)

Quick wins
€170 4 fixes in ~120 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
/hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€10,041,670 / month at risk

~€120,500,035 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveGDPREAA
  • No privacy policy link detected
    GDPR: EUR 10,000 – EUR 20,000,000
  • 1 advertising/retargeting trackers detected
    GDPR: EUR 10,000 – EUR 20,000,000
  • Trackers detected but no cookie policy found
    GDPR: EUR 5,000 – EUR 10,000,000

+10 more

Bandwidth Waste

€2.88 /mo

38879.4 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~3.9 MB per page load
    Saves €2.88/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

25
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
80
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
75
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

4.81 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

17.57 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

310 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

1.729

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

9.99 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

36.56 s

Detailed Report

Audit breakdown by category with detailed findings.

25

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
/media.fundable.com/companies/203930/covers/screen-shot-2...0.0 ms3.3 MiB
/media.fundable.com/companies/317505/covers/phynx-final-d...0.0 ms1.0 MiB
www.fundable.com/web/v2/images/home/resolve/stats.png0.0 ms853.9 KiB
www.fundable.com/web/v2/images/home/transend/stats.png0.0 ms711.5 KiB
s3.amazonaws.com/media.fundable.com/companies/301408/covers/title-x8quelmcgf.png0.0 ms617.3 KiB
/media.fundable.com/companies/155637/covers/cover-slide-f...0.0 ms571.8 KiB
s3.amazonaws.com/media.fundable.com/companies/184618/covers/1-lvmiorkjcj.png0.0 ms399.0 KiB
www.fundable.com/web/v2/images/home/arcimoto/background-min.jpeg0.0 ms363.6 KiB
s3.amazonaws.com/media.fundable.com/companies/232161/covers/cover-qmqx0l4a7r.png0.0 ms298.6 KiB
www.fundable.com/web/v2/images/home/rhone/background-min.jpeg0.0 ms296.4 KiB
www.fundable.com/web/v2/images/home/unistellar/background-min.jpeg0.0 ms293.1 KiB
www.fundable.com/web/v2/images/home/transend/background-min.jpeg0.0 ms243.8 KiB
/media.fundable.com/companies/297201/covers/smartiz-pitch...0.0 ms204.8 KiB
www.fundable.com/web/v2/images/home/resolve/background-min.jpeg0.0 ms198.2 KiB
/media.fundable.com/companies/309643/covers/footballmoney...0.0 ms172.4 KiB
/media.fundable.com/companies/190565/covers/slide1-kkljnb...0.0 ms168.1 KiB
www.fundable.com/web/v2/images/home/awkward/background-min.jpeg0.0 ms159.4 KiB
/media.fundable.com/companies/307322/covers/slide1-gdyqc7...0.0 ms96.9 KiB
www.fundable.com/web/v2/images/home/arcimoto/stats.png0.0 ms94.6 KiB
s3.amazonaws.com/media.fundable.com/companies/181156/covers/1-soqdhbt58f.png0.0 ms92.4 KiB
www.fundable.com/web/v2/framework/compiled.css?_cache=17769017480.0 ms87.0 KiB
www.fundable.com/web/v2/images/home/unistellar/stats.png0.0 ms86.1 KiB
www.fundable.com/web/v2/images/home/awkward/stats.png0.0 ms84.8 KiB
www.fundable.com/web/v2/images/home/rhone/stats.png0.0 ms80.1 KiB
/media.fundable.com/companies/311594/covers/1748982880916...0.0 ms75.6 KiB
/media.fundable.com/companies/311091/covers/screenshot-20...0.0 ms68.4 KiB
/media.fundable.com/companies/232158/covers/ae-cover-t7hj...0.0 ms65.5 KiB
cdn.optimizely.com/js/2135370051.js120.0 s65.5 KiB
www.fundable.com/sco/fundable/vendor.js?cache=17769017480.0 ms61.9 KiB
s3.amazonaws.com/media.fundable.com/companies/185151/covers/1-ar9ttc5hev.png0.0 ms59.4 KiB
www.fundable.com/web/v2/framework/compiled.js?_cache=17769017480.0 ms57.7 KiB
/next-integrations/actions/google-analytics-4-web/aeadee7...0.0 ms57.7 KiB
www.fundable.com/sco/fundable/fundable.js?cache=17769017480.0 ms55.1 KiB
/media.fundable.com/companies/296688/covers/1749584430984...0.0 ms53.3 KiB
js.hs-analytics.net/analytics/1776901800000/459884.js300.0 s42.8 KiB
js.usemessages.com/conversations-embed.js600.0 s33.0 KiB
cdn.segment.com/analytics.js/v1/fx25yu1p41/analytics.min.js120.0 s28.8 KiB
js.hs-banner.com/v2/459884/banner.js300.0 s24.2 KiB
wchat.freshchat.com/js/widget.js900.0 s22.2 KiB
www.fundable.com/shared/fonts/pictos-web.woff0.0 ms12.8 KiB
/web/v2/framework/ui-kit/ui-kit-fundable/css/style.css?_c...0.0 ms10.9 KiB
cdn.segment.com/next-integrations/actions/3962/1faa179dfb20d0a3f5a0.js0.0 ms9.2 KiB
www.fundable.com/sco/fundable/fundable.css?_cache=17769017480.0 ms8.0 KiB
www.fundable.com/web/v1/js/jquery/jquery-cycle.js?_cache=17769017480.0 ms7.2 KiB
use.typekit.net/pek2bhn.js600.0 s6.8 KiB
www.fundable.com/web/v1/js/fundable/ui.js?_cache=17769017480.0 ms5.7 KiB
www.fundable.com/web/v2/js/jquery/colpick.js?_cache=17769017480.0 ms5.0 KiB
www.fundable.com/web/v1/js/fundable/common.js?_cache=17769017480.0 ms4.7 KiB
/web/v1/js/uploadifive/jquery.uploadifive.min.js?_cache=1...0.0 ms4.3 KiB
js.hsadspixel.net/pixels.js600.0 s3.9 KiB
www.fundable.com/web/v1/js/other/form2js.js?_cache=17769017480.0 ms3.2 KiB
www.fundable.com/web/v1/js/jquery/jquery-transit.js?_cache=17769017480.0 ms2.9 KiB
www.fundable.com/web/v1/js/fundable/utilities.js?_cache=17769017480.0 ms2.6 KiB
www.fundable.com/web/v2/css/colpick.css?_cache=17769017480.0 ms2.1 KiB
www.fundable.com/web/v1/js/jquery/jquery-easing.js?_cache=17769017480.0 ms2.0 KiB
www.fundable.com/web/v1/js/other/date-format.js?_cache=17769017480.0 ms2.0 KiB
www.fundable.com/web/v1/js/other/accounting.min.js?_cache=17769017480.0 ms1.5 KiB
www.fundable.com/web/v1/js/fundable/config.js?_cache=17769017480.0 ms1.0 KiB
js-na1.hs-scripts.com/459884.js0.0 ms1.0 KiB
www.fundable.com/shared/js/fa.js?_cache=17769017480.0 ms859 B
static.hsappstatic.net/whisper-core/ex/whisper-core.js60.0 s814 B
www.fundable.com/shared/css/pictos.css?_cache=17769017480.0 ms669 B
www.fundable.com/web/v2/js/fundable/home.js?_cache=17769017480.0 ms653 B
/p.gif?s=1&k=pek2bhn&ht=tk&h=www.fundable.com&f=139.140.1...604800.0 s205 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:1.72904] map[node:map[boundingRect:map[bottom:3632 height:3032 left:0 right:412 top:600 width:412] lhId:page-1-SECTION nodeLabel:Featured Companies on Fundable NutriSelect.ai, Inc. AI App for Dietary Suppleme… path:1,HTML,1,BODY,4,SECTION selector:body > section.company-tile-grid-1 snippet:<section class="company-tile-grid-1"> type:node] score:1] map[node:map[boundingRect:map[bottom:3632 height:3032 left:0 right:412 top:600 width:412] lhId:page-1-SECTION nodeLabel:Featured Companies on Fundable NutriSelect.ai, Inc. AI App for Dietary Suppleme… path:1,HTML,1,BODY,4,SECTION selector:body > section.company-tile-grid-1 snippet:<section class="company-tile-grid-1"> type:node] score:0.72904]]

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-DIV
nodeLabel: body > header.hero-1 > div.slide-wrapper > div.slide
path: 1,HTML,1,BODY,2,HEADER,0,DIV,1,DIV
selector: body > header.hero-1 > div.slide-wrapper > div.slide
snippet: <div class="slide cycle-slide" style="background-image: url(&quot;/web/v2/images/home/arcimoto/background-min.jpeg&quot;);">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
www.fundable.com/web/v2/framework/compiled.css?_cache=177690174887.0 KiB1.7 s
www.fundable.com/web/v1/js/fundable/config.js?_cache=17769017481.0 KiB
www.fundable.com/web/v1/js/fundable/common.js?_cache=17769017484.7 KiB
www.fundable.com/web/v1/js/other/form2js.js?_cache=17769017483.2 KiB
www.fundable.com/web/v1/js/fundable/utilities.js?_cache=17769017482.6 KiB
www.fundable.com/web/v1/js/other/accounting.min.js?_cache=17769017481.5 KiB
www.fundable.com/web/v1/js/fundable/ui.js?_cache=17769017485.7 KiB151 ms
www.fundable.com/shared/js/fa.js?_cache=1776901748859 B
www.fundable.com/web/v2/js/jquery/colpick.js?_cache=17769017485.0 KiB
/web/v1/js/uploadifive/jquery.uploadifive.min.js?_cache=1...4.3 KiB
www.fundable.com/web/v1/js/jquery/jquery-cycle.js?_cache=17769017487.2 KiB
www.fundable.com/web/v2/framework/compiled.js?_cache=177690174857.7 KiB301 ms
www.fundable.com/web/v1/js/other/date-format.js?_cache=17769017482.0 KiB
www.fundable.com/web/v2/js/fundable/home.js?_cache=1776901748653 B
/web/v2/framework/ui-kit/ui-kit-fundable/css/style.css?_c...10.9 KiB151 ms
cdn.optimizely.com/js/2135370051.js65.5 KiB1.9 s
wchat.freshchat.com/js/widget.js22.2 KiB1.3 s
www.fundable.com/sco/fundable/fundable.css?_cache=17769017488.0 KiB151 ms
www.fundable.com/web/v1/js/jquery/jquery-transit.js?_cache=17769017482.9 KiB
www.fundable.com/web/v1/js/jquery/jquery-easing.js?_cache=17769017482.0 KiB151 ms
www.fundable.com/shared/css/pictos.css?_cache=1776901748669 B
www.fundable.com/web/v2/css/colpick.css?_cache=17769017482.1 KiB
use.typekit.net/pek2bhn.js6.8 KiB151 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
FUNDED div.company-tile > a > div > div.photo
/media.fundable.com/companies/203930/covers/screen-shot-2...3.3 MiB2.6 MiB
div.company-tile > a > div > div.photo div.company-tile > a > div > div.photo
s3.amazonaws.com/media.fundable.com/companies/301408/covers/title-x8quelmcgf.png616.9 KiB532.6 KiB
FUNDED div.company-tile > a > div > div.photo
/media.fundable.com/companies/155637/covers/cover-slide-f...571.4 KiB496.4 KiB
FUNDED div.company-tile > a > div > div.photo
s3.amazonaws.com/media.fundable.com/companies/184618/covers/1-lvmiorkjcj.png398.7 KiB348.0 KiB
FUNDED div.company-tile > a > div > div.photo
s3.amazonaws.com/media.fundable.com/companies/232161/covers/cover-qmqx0l4a7r.png298.2 KiB240.4 KiB
div.company-tile > a > div > div.photo div.company-tile > a > div > div.photo
/media.fundable.com/companies/317505/covers/phynx-final-d...1.0 MiB230.2 KiB
FUNDED div.company-tile > a > div > div.photo
/media.fundable.com/companies/190565/covers/slide1-kkljnb...167.8 KiB99.0 KiB
FUNDED div.company-tile > a > div > div.photo
s3.amazonaws.com/media.fundable.com/companies/181156/covers/1-soqdhbt58f.png92.0 KiB41.3 KiB
div.company-tile > a > div > div.photo div.company-tile > a > div > div.photo
/media.fundable.com/companies/309643/covers/footballmoney...172.0 KiB22.0 KiB
FUNDED div.company-tile > a > div > div.photo
s3.amazonaws.com/media.fundable.com/companies/185151/covers/1-ar9ttc5hev.png59.1 KiB8.4 KiB
FUNDED div.company-tile > a > div > div.photo
/media.fundable.com/companies/232158/covers/ae-cover-t7hj...65.1 KiB7.3 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.0 s
URLTime Spent
fundable.com/1.0 s
www.fundable.com/0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Featured Companies on Fundable NutriSelect.ai, Inc. AI App for Dietary Suppleme… body > section.company-tile-grid-1
1.000
Featured Companies on Fundable NutriSelect.ai, Inc. AI App for Dietary Suppleme… body > section.company-tile-grid-1
0.729

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 160 ms 17.8 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 160 ms 8.3 KiB
URLTransfer SizeEst Savings
www.fundable.com/web/v2/framework/compiled.js?_cache=177690174857.5 KiB8.3 KiB

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 480 ms 83.9 KiB
URLTransfer SizeEst Savings
www.fundable.com/web/v2/framework/compiled.css?_cache=177690174886.8 KiB83.9 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation1.6 s
Other1.0 s
Style & Layout445 ms
Script Parsing & Compilation251 ms
Rendering91 ms
Parse HTML & CSS77 ms
Garbage Collection20 ms

More information about the performance of your application. These numbers don't directly affect the Performance score.

Optimize DOM size
Forced reflow
LCP breakdown
Optimize viewport for mobile
User Timing marks and measures 11 user timings
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 5 animated elements found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 180 ms
Server Backend Latencies 200 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 330 ms
INP breakdown
80

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div.Nav__component__3p5vb > div.layout__wrapper__3Ecno > button.Nav__mobileNavOpen___8nmr div > div.Nav__component__3p5vb > div.layout__wrapper__3Ecno > button.Nav__mobileNavOpen___8nmr

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
GET STARTED div.bg-overlay-x > div.content > div.text > a.btn
@  Clearwater, FL, United States a > div > div.location > div
@  Trélex, Switzerland a > div > div.location > div
@  Fort Lauderdale, FL, United States a > div > div.location > div
@  Fort Lauderdale, FL, United States a > div > div.location > div
@  Private a > div > div.location > div
@  Long Beach, CA, United States a > div > div.location > div
@  Palo Alto, CA, United States a > div > div.location > div
@  Jersey City, NJ, United States a > div > div.location > div
View More div.span12 > div.company-tile-grid > div > a.btn
Funding Committed section.callout-1 > div > div.span6 > p
Accredited Investors section.callout-1 > div > div.span6 > p
@  Costa Mesa, CA a > div > div.location > div
RAISED $2,000,000 div > div.metric > div.text > strong
@  Boston, MA a > div > div.location > div
RAISED $5,200,000 div > div.metric > div.text > strong
@  Fremont, CA a > div > div.location > div
RAISED $3,000,000 div > div.metric > div.text > strong
@  Las Vegas, NV a > div > div.location > div
RAISED $2,216,900 div > div.metric > div.text > strong
@  France a > div > div.location > div
RAISED $430,646 div > div.metric > div.text > strong
@  Private a > div > div.location > div
RAISED $3,068,000 div > div.metric > div.text > strong
@  Dallas, TX a > div > div.location > div
RAISED $712,400 div > div.metric > div.text > strong
@  Temecula, CA a > div > div.location > div
RAISED $500,000 div > div.metric > div.text > strong
View More div.span12 > div.company-tile-grid > div > a.btn
Host your raise on Fundable div.plans > div.plan > ul > li
Secure data room for prospective investor materials div.plans > div.plan > ul > li
Email-only support div.plans > div.plan > ul > li
Marketing outreach templates div.plans > div.plan > ul > li
Membership in Startups.com Accelerator div.plans > div.plan > ul > li
Online Accelerator div.layout__c1of6__reh-q > a.PlatformFooter__product__22OKY > div.PlatformFooter__productTag__zegMN > span
Startup Planning div.layout__c1of6__reh-q > a.PlatformFooter__product__22OKY > div.PlatformFooter__productTag__zegMN > span
Access Mentors div.layout__c1of6__reh-q > a.PlatformFooter__product__22OKY > div.PlatformFooter__productTag__zegMN > span
Secure Funding div.layout__c1of6__reh-q > a.PlatformFooter__product__22OKY > div.PlatformFooter__productTag__zegMN > span
Reach Customers div.layout__c1of6__reh-q > a.PlatformFooter__product__22OKY > div.PlatformFooter__productTag__zegMN > span
Virtual Assistants div.layout__c1of6__reh-q > a.PlatformFooter__product__22OKY > div.PlatformFooter__productTag__zegMN > span
Copyright © 2026 Startups.com. All rights reserved. section.PlatformFooter__component__3q3YT > div.layout__wrapper__3Ecno > div.layout__c1of1__3k6dX > p
Fundable is a software as a service funding platform. Fundable is not a registe… body > div > div > p

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
GET STARTED div.Footer__wrapper__2J7pb > div.Footer__column__1bqCR > a > h6.Footer__categoryFirst__If9MK

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta head > meta

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js html.js

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
ARIA attributes are used as specified for the element's role
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
Deprecated ARIA roles were not used
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Image elements have `[alt]` attributes
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
75

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Basic div.plan > div.title > div > a.btn
Premium div.plan > div.title > div > a.btn

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Page has successful HTTP status code
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`
Image elements have `[alt]` attributes

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

48
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
82
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
69
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.46 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

3.15 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

1.250

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.52 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

6.19 s

Detailed Report

Audit breakdown by category with detailed findings.

48

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
/media.fundable.com/companies/203930/covers/screen-shot-2...0.0 ms3.3 MiB
/media.fundable.com/companies/317505/covers/phynx-final-d...0.0 ms1.0 MiB
www.fundable.com/web/v2/images/home/resolve/stats.png0.0 ms853.9 KiB
www.fundable.com/web/v2/images/home/transend/stats.png0.0 ms711.5 KiB
s3.amazonaws.com/media.fundable.com/companies/301408/covers/title-x8quelmcgf.png0.0 ms617.4 KiB
/media.fundable.com/companies/155637/covers/cover-slide-f...0.0 ms571.8 KiB
s3.amazonaws.com/media.fundable.com/companies/184618/covers/1-lvmiorkjcj.png0.0 ms399.1 KiB
www.fundable.com/web/v2/images/home/arcimoto/background-min.jpeg0.0 ms363.6 KiB
s3.amazonaws.com/media.fundable.com/companies/232161/covers/cover-qmqx0l4a7r.png0.0 ms298.6 KiB
www.fundable.com/web/v2/images/home/rhone/background-min.jpeg0.0 ms296.4 KiB
www.fundable.com/web/v2/images/home/unistellar/background-min.jpeg0.0 ms293.1 KiB
www.fundable.com/web/v2/images/home/transend/background-min.jpeg0.0 ms243.8 KiB
/media.fundable.com/companies/297201/covers/smartiz-pitch...0.0 ms204.8 KiB
www.fundable.com/web/v2/images/home/resolve/background-min.jpeg0.0 ms198.2 KiB
/media.fundable.com/companies/309643/covers/footballmoney...0.0 ms172.4 KiB
/media.fundable.com/companies/190565/covers/slide1-kkljnb...0.0 ms168.2 KiB
www.fundable.com/web/v2/images/home/awkward/background-min.jpeg0.0 ms159.4 KiB
/media.fundable.com/companies/307322/covers/slide1-gdyqc7...0.0 ms96.9 KiB
www.fundable.com/web/v2/images/home/arcimoto/stats.png0.0 ms94.6 KiB
s3.amazonaws.com/media.fundable.com/companies/181156/covers/1-soqdhbt58f.png0.0 ms92.4 KiB
www.fundable.com/web/v2/framework/compiled.css?_cache=17769017670.0 ms87.0 KiB
www.fundable.com/web/v2/images/home/unistellar/stats.png0.0 ms86.1 KiB
www.fundable.com/web/v2/images/home/awkward/stats.png0.0 ms84.8 KiB
www.fundable.com/web/v2/images/home/rhone/stats.png0.0 ms80.1 KiB
/media.fundable.com/companies/311594/covers/1748982880916...0.0 ms75.7 KiB
/media.fundable.com/companies/311091/covers/screenshot-20...0.0 ms68.5 KiB
/media.fundable.com/companies/232158/covers/ae-cover-t7hj...0.0 ms65.5 KiB
cdn.optimizely.com/js/2135370051.js120.0 s65.5 KiB
www.fundable.com/sco/fundable/vendor.js?cache=17769017670.0 ms61.8 KiB
s3.amazonaws.com/media.fundable.com/companies/185151/covers/1-ar9ttc5hev.png0.0 ms59.4 KiB
www.fundable.com/web/v2/framework/compiled.js?_cache=17769017670.0 ms57.7 KiB
/next-integrations/actions/google-analytics-4-web/aeadee7...0.0 ms57.7 KiB
www.fundable.com/sco/fundable/fundable.js?cache=17769017670.0 ms55.1 KiB
/media.fundable.com/companies/296688/covers/1749584430984...0.0 ms53.3 KiB
js.hs-analytics.net/analytics/1776901800000/459884.js300.0 s42.8 KiB
js.usemessages.com/conversations-embed.js600.0 s33.0 KiB
cdn.segment.com/analytics.js/v1/fx25yu1p41/analytics.min.js120.0 s28.8 KiB
js.hs-banner.com/v2/459884/banner.js300.0 s24.2 KiB
wchat.freshchat.com/js/widget.js900.0 s22.2 KiB
www.fundable.com/shared/fonts/pictos-web.woff0.0 ms12.8 KiB
/web/v2/framework/ui-kit/ui-kit-fundable/css/style.css?_c...0.0 ms10.9 KiB
cdn.segment.com/next-integrations/actions/3962/1faa179dfb20d0a3f5a0.js0.0 ms9.2 KiB
www.fundable.com/sco/fundable/fundable.css?_cache=17769017670.0 ms8.0 KiB
www.fundable.com/web/v1/js/jquery/jquery-cycle.js?_cache=17769017670.0 ms7.2 KiB
use.typekit.net/pek2bhn.js600.0 s6.8 KiB
www.fundable.com/web/v1/js/fundable/ui.js?_cache=17769017670.0 ms5.7 KiB
www.fundable.com/web/v2/js/jquery/colpick.js?_cache=17769017670.0 ms5.0 KiB
www.fundable.com/web/v1/js/fundable/common.js?_cache=17769017670.0 ms4.7 KiB
/web/v1/js/uploadifive/jquery.uploadifive.min.js?_cache=1...0.0 ms4.3 KiB
js.hsadspixel.net/pixels.js600.0 s3.9 KiB
www.fundable.com/web/v1/js/other/form2js.js?_cache=17769017670.0 ms3.2 KiB
www.fundable.com/web/v1/js/jquery/jquery-transit.js?_cache=17769017670.0 ms2.9 KiB
www.fundable.com/web/v1/js/fundable/utilities.js?_cache=17769017670.0 ms2.6 KiB
www.fundable.com/web/v2/css/colpick.css?_cache=17769017670.0 ms2.1 KiB
www.fundable.com/web/v1/js/jquery/jquery-easing.js?_cache=17769017670.0 ms2.0 KiB
www.fundable.com/web/v1/js/other/date-format.js?_cache=17769017670.0 ms2.0 KiB
www.fundable.com/web/v1/js/other/accounting.min.js?_cache=17769017670.0 ms1.5 KiB
www.fundable.com/web/v1/js/fundable/config.js?_cache=17769017670.0 ms1.0 KiB
js-na1.hs-scripts.com/459884.js0.0 ms1.0 KiB
www.fundable.com/shared/js/fa.js?_cache=17769017670.0 ms859 B
static.hsappstatic.net/whisper-core/ex/whisper-core.js60.0 s755 B
www.fundable.com/shared/css/pictos.css?_cache=17769017670.0 ms669 B
www.fundable.com/web/v2/js/fundable/home.js?_cache=17769017670.0 ms653 B
hs.startups.com/hs-fs/hubfs/Zqsg6Iuw.png?width=108&height=1081209600.0 s2.6 KiB
/p.gif?s=1&k=pek2bhn&ht=tk&h=www.fundable.com&f=139.140.1...604800.0 s205 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:1.250098] map[node:map[boundingRect:map[bottom:1806 height:932 left:0 right:1350 top:874 width:1350] lhId:page-20-SECTION nodeLabel:Featured Companies on Fundable NutriSelect.ai, Inc. AI App for Dietary Suppleme… path:1,HTML,1,BODY,4,SECTION selector:body > section.company-tile-grid-1 snippet:<section class="company-tile-grid-1"> type:node] score:0.613554] map[node:map[boundingRect:map[bottom:1806 height:932 left:0 right:1350 top:874 width:1350] lhId:page-20-SECTION nodeLabel:Featured Companies on Fundable NutriSelect.ai, Inc. AI App for Dietary Suppleme… path:1,HTML,1,BODY,4,SECTION selector:body > section.company-tile-grid-1 snippet:<section class="company-tile-grid-1"> type:node] score:0.613554] map[node:map[boundingRect:map[bottom:874 height:850 left:0 right:1350 top:24 width:1350] lhId:page-19-HEADER nodeLabel:Startup Fundraising Platform Start and manage a professional fundraise to attr… path:1,HTML,1,BODY,2,HEADER selector:body > header.hero-1 snippet:<header class="hero-1"> type:node] score:0.017778] map[node:map[boundingRect:map[bottom:612 height:326 left:75 right:675 top:286 width:600] lhId:page-18-DIV nodeLabel:div.bg-overlay-y > div.bg-overlay-x > div.content > div.text path:1,HTML,1,BODY,2,HEADER,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV selector:div.bg-overlay-y > div.bg-overlay-x > div.content > div.text snippet:<div class="text"> type:node] score:0.005212 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:834 height:210 left:735 right:1275 top:624 width:540] lhId:page-11-IMG nodeLabel:div.bg-overlay-x > div.content > div.stat > img path:1,HTML,1,BODY,2,HEADER,0,DIV,3,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,IMG selector:div.bg-overlay-x > div.content > div.stat > img snippet:<img src="/web/v2/images/home/awkward/stats.png" "=""> type:node]]] type:subitems]]]
headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.025248] map[node:map[boundingRect:map[bottom:834 height:413 left:735 right:1275 top:421 width:540] lhId:page-2-IMG nodeLabel:div.bg-overlay-x > div.content > div.stat > img path:1,HTML,1,BODY,2,HEADER,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,IMG selector:div.bg-overlay-x > div.content > div.stat > img snippet:<img src="/web/v2/images/home/transend/stats.png" "=""> type:node] score:0.02137] map[node:map[boundingRect:map[bottom:940 height:245 left:1168 right:1350 top:695 width:182] lhId:page-21-IFRAME nodeLabel:body > div#hubspot-messages-iframe-container > iframe#hubspot-conversations-iframe path:1,HTML,1,BODY,16,DIV,1,IFRAME selector:body > div#hubspot-messages-iframe-container > iframe#hubspot-conversations-iframe snippet:<iframe src="https://app.hubspot.com/conversations-visitor/459884/threads/utk/74c0dee00…" id="hubspot-conversations-iframe" allowfullscreen="" data-test-id="chat-widget-iframe"> type:node] score:0.003878]]

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
FUNDED div.company-tile > a > div > div.photo
/media.fundable.com/companies/203930/covers/screen-shot-2...3.3 MiB2.6 MiB
div.bg-overlay-x > div.content > div.stat > img div.bg-overlay-x > div.content > div.stat > img
www.fundable.com/web/v2/images/home/resolve/stats.png852.7 KiB818.8 KiB
div.bg-overlay-x > div.content > div.stat > img div.bg-overlay-x > div.content > div.stat > img
www.fundable.com/web/v2/images/home/transend/stats.png710.6 KiB674.3 KiB
div.company-tile > a > div > div.photo div.company-tile > a > div > div.photo
s3.amazonaws.com/media.fundable.com/companies/301408/covers/title-x8quelmcgf.png616.9 KiB532.6 KiB
FUNDED div.company-tile > a > div > div.photo
/media.fundable.com/companies/155637/covers/cover-slide-f...571.4 KiB496.4 KiB
FUNDED div.company-tile > a > div > div.photo
s3.amazonaws.com/media.fundable.com/companies/184618/covers/1-lvmiorkjcj.png398.7 KiB348.0 KiB
FUNDED div.company-tile > a > div > div.photo
s3.amazonaws.com/media.fundable.com/companies/232161/covers/cover-qmqx0l4a7r.png298.2 KiB240.4 KiB
div.company-tile > a > div > div.photo div.company-tile > a > div > div.photo
/media.fundable.com/companies/317505/covers/phynx-final-d...1.0 MiB230.2 KiB
FUNDED div.company-tile > a > div > div.photo
/media.fundable.com/companies/190565/covers/slide1-kkljnb...167.8 KiB99.0 KiB
div.bg-overlay-x > div.content > div.stat > img div.bg-overlay-x > div.content > div.stat > img
www.fundable.com/web/v2/images/home/arcimoto/stats.png94.3 KiB76.7 KiB
div.bg-overlay-x > div.content > div.stat > img div.bg-overlay-x > div.content > div.stat > img
www.fundable.com/web/v2/images/home/unistellar/stats.png85.8 KiB68.6 KiB
div.bg-overlay-x > div.content > div.stat > img div.bg-overlay-x > div.content > div.stat > img
www.fundable.com/web/v2/images/home/awkward/stats.png84.5 KiB67.5 KiB
div.bg-overlay-x > div.content > div.stat > img div.bg-overlay-x > div.content > div.stat > img
www.fundable.com/web/v2/images/home/rhone/stats.png79.9 KiB64.0 KiB
FUNDED div.company-tile > a > div > div.photo
s3.amazonaws.com/media.fundable.com/companies/181156/covers/1-soqdhbt58f.png92.0 KiB41.3 KiB
div.company-tile > a > div > div.photo div.company-tile > a > div > div.photo
/media.fundable.com/companies/309643/covers/footballmoney...172.0 KiB22.0 KiB
FUNDED div.company-tile > a > div > div.photo
s3.amazonaws.com/media.fundable.com/companies/185151/covers/1-ar9ttc5hev.png59.1 KiB8.4 KiB
FUNDED div.company-tile > a > div > div.photo
/media.fundable.com/companies/232158/covers/ae-cover-t7hj...65.1 KiB7.3 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-17-DIV
nodeLabel: body > header.hero-1 > div.slide-wrapper > div.slide
path: 1,HTML,1,BODY,2,HEADER,0,DIV,1,DIV
selector: body > header.hero-1 > div.slide-wrapper > div.slide
snippet: <div class="slide cycle-slide" style="background-image: url(&quot;/web/v2/images/home/transend/background-min.jpeg&quot;);">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
www.fundable.com/web/v2/framework/compiled.js?_cache=177690176757.7 KiB80 ms
www.fundable.com/web/v2/framework/compiled.css?_cache=177690176787.0 KiB280 ms
www.fundable.com/web/v1/js/fundable/utilities.js?_cache=17769017672.6 KiB
www.fundable.com/web/v1/js/fundable/config.js?_cache=17769017671.0 KiB
www.fundable.com/web/v1/js/other/accounting.min.js?_cache=17769017671.5 KiB
www.fundable.com/web/v1/js/other/date-format.js?_cache=17769017672.0 KiB
www.fundable.com/web/v1/js/other/form2js.js?_cache=17769017673.2 KiB
www.fundable.com/web/v1/js/fundable/common.js?_cache=17769017674.7 KiB
/web/v1/js/uploadifive/jquery.uploadifive.min.js?_cache=1...4.3 KiB
www.fundable.com/web/v2/css/colpick.css?_cache=17769017672.1 KiB
www.fundable.com/shared/css/pictos.css?_cache=1776901767669 B
www.fundable.com/shared/js/fa.js?_cache=1776901767859 B
www.fundable.com/web/v1/js/fundable/ui.js?_cache=17769017675.7 KiB
www.fundable.com/web/v2/js/jquery/colpick.js?_cache=17769017675.0 KiB
www.fundable.com/web/v1/js/jquery/jquery-cycle.js?_cache=17769017677.2 KiB
www.fundable.com/web/v1/js/jquery/jquery-transit.js?_cache=17769017672.9 KiB
www.fundable.com/web/v2/js/fundable/home.js?_cache=1776901767653 B
/web/v2/framework/ui-kit/ui-kit-fundable/css/style.css?_c...10.9 KiB
www.fundable.com/web/v1/js/jquery/jquery-easing.js?_cache=17769017672.0 KiB
www.fundable.com/sco/fundable/fundable.css?_cache=17769017678.0 KiB80 ms
cdn.optimizely.com/js/2135370051.js65.5 KiB425 ms
wchat.freshchat.com/js/widget.js22.2 KiB316 ms
use.typekit.net/pek2bhn.js6.8 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 492 ms
URLTime Spent
fundable.com/492 ms
www.fundable.com/0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Featured Companies on Fundable NutriSelect.ai, Inc. AI App for Dietary Suppleme… body > section.company-tile-grid-1
0.614
Featured Companies on Fundable NutriSelect.ai, Inc. AI App for Dietary Suppleme… body > section.company-tile-grid-1
0.614
div.bg-overlay-x > div.content > div.stat > img div.bg-overlay-x > div.content > div.stat > img
0.021
Startup Fundraising Platform Start and manage a professional fundraise to attr… body > header.hero-1
0.018
div.bg-overlay-y > div.bg-overlay-x > div.content > div.text div.bg-overlay-y > div.bg-overlay-x > div.content > div.text
0.005
body > div#hubspot-messages-iframe-container > iframe#hubspot-conversations-iframe body > div#hubspot-messages-iframe-container > iframe#hubspot-conversations-iframe
0.004

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 100 ms 84.2 KiB
URLTransfer SizeEst Savings
www.fundable.com/web/v2/framework/compiled.css?_cache=177690176786.8 KiB84.2 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 17.8 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 8.3 KiB
URLTransfer SizeEst Savings
www.fundable.com/web/v2/framework/compiled.js?_cache=177690176757.6 KiB8.3 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div.bg-overlay-x > div.content > div.stat > img div.bg-overlay-x > div.content > div.stat > img
www.fundable.com/web/v2/images/home/transend/stats.png
div.bg-overlay-x > div.content > div.stat > img div.bg-overlay-x > div.content > div.stat > img
www.fundable.com/web/v2/images/home/transend/stats.png
div.bg-overlay-x > div.content > div.stat > img div.bg-overlay-x > div.content > div.stat > img
www.fundable.com/web/v2/images/home/resolve/stats.png
div.bg-overlay-x > div.content > div.stat > img div.bg-overlay-x > div.content > div.stat > img
www.fundable.com/web/v2/images/home/arcimoto/stats.png
div.bg-overlay-x > div.content > div.stat > img div.bg-overlay-x > div.content > div.stat > img
www.fundable.com/web/v2/images/home/rhone/stats.png
div.bg-overlay-x > div.content > div.stat > img div.bg-overlay-x > div.content > div.stat > img
www.fundable.com/web/v2/images/home/unistellar/stats.png
div.bg-overlay-x > div.content > div.stat > img div.bg-overlay-x > div.content > div.stat > img
www.fundable.com/web/v2/images/home/awkward/stats.png

More information about the performance of your application. These numbers don't directly affect the Performance score.

Optimize DOM size
Forced reflow
LCP breakdown
Optimize viewport for mobile
Max Potential First Input Delay 50 ms
User Timing marks and measures 11 user timings
JavaScript execution time 0.3 s
Minimizes main-thread work 0.9 s
Avoid long main-thread tasks 1 long task found
Avoid non-composited animations 4 animated elements found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 170 ms
Server Backend Latencies 180 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 310 ms
INP breakdown
82

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
GET STARTED div.bg-overlay-x > div.content > div.text > a.btn
@  Clearwater, FL, United States a > div > div.location > div
@  Trélex, Switzerland a > div > div.location > div
@  Fort Lauderdale, FL, United States a > div > div.location > div
@  Fort Lauderdale, FL, United States a > div > div.location > div
@  Private a > div > div.location > div
@  Long Beach, CA, United States a > div > div.location > div
@  Palo Alto, CA, United States a > div > div.location > div
@  Jersey City, NJ, United States a > div > div.location > div
View More div.span12 > div.company-tile-grid > div > a.btn
Funding Committed section.callout-1 > div > div.span6 > p
Accredited Investors section.callout-1 > div > div.span6 > p
@  Costa Mesa, CA a > div > div.location > div
RAISED $2,000,000 div > div.metric > div.text > strong
@  Boston, MA a > div > div.location > div
RAISED $5,200,000 div > div.metric > div.text > strong
@  Fremont, CA a > div > div.location > div
RAISED $3,000,000 div > div.metric > div.text > strong
@  Las Vegas, NV a > div > div.location > div
RAISED $2,216,900 div > div.metric > div.text > strong
@  France a > div > div.location > div
RAISED $430,646 div > div.metric > div.text > strong
@  Private a > div > div.location > div
RAISED $3,068,000 div > div.metric > div.text > strong
@  Dallas, TX a > div > div.location > div
RAISED $712,400 div > div.metric > div.text > strong
@  Temecula, CA a > div > div.location > div
RAISED $500,000 div > div.metric > div.text > strong
View More div.span12 > div.company-tile-grid > div > a.btn
Host your raise on Fundable div.plans > div.plan > ul > li
Secure data room for prospective investor materials div.plans > div.plan > ul > li
Email-only support div.plans > div.plan > ul > li
Marketing outreach templates div.plans > div.plan > ul > li
Membership in Startups.com Accelerator div.plans > div.plan > ul > li
Online Accelerator div.layout__c1of6__reh-q > a.PlatformFooter__product__22OKY > div.PlatformFooter__productTag__zegMN > span
Startup Planning div.layout__c1of6__reh-q > a.PlatformFooter__product__22OKY > div.PlatformFooter__productTag__zegMN > span
Access Mentors div.layout__c1of6__reh-q > a.PlatformFooter__product__22OKY > div.PlatformFooter__productTag__zegMN > span
Secure Funding div.layout__c1of6__reh-q > a.PlatformFooter__product__22OKY > div.PlatformFooter__productTag__zegMN > span
Reach Customers div.layout__c1of6__reh-q > a.PlatformFooter__product__22OKY > div.PlatformFooter__productTag__zegMN > span
Virtual Assistants div.layout__c1of6__reh-q > a.PlatformFooter__product__22OKY > div.PlatformFooter__productTag__zegMN > span
Copyright © 2026 Startups.com. All rights reserved. section.PlatformFooter__component__3q3YT > div.layout__wrapper__3Ecno > div.layout__c1of1__3k6dX > p
Fundable is a software as a service funding platform. Fundable is not a registe… body > div > div > p

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
GET STARTED div.Footer__wrapper__2J7pb > div.Footer__column__1bqCR > a > h6.Footer__categoryFirst__If9MK

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.bg-overlay-x > div.content > div.stat > img div.bg-overlay-x > div.content > div.stat > img
div.bg-overlay-x > div.content > div.stat > img div.bg-overlay-x > div.content > div.stat > img

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
ARIA attributes are used as specified for the element's role
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
Buttons have an accessible name
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
69

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.bg-overlay-x > div.content > div.stat > img div.bg-overlay-x > div.content > div.stat > img
div.bg-overlay-x > div.content > div.stat > img div.bg-overlay-x > div.content > div.stat > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Basic div.plan > div.title > div > a.btn
Premium div.plan > div.title > div > a.btn

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Page has successful HTTP status code
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback