Website review, no card needed
startup.network website review
Visit site (opens in a new tab)Reviewed 24 October 202642 issues · 90 checks
This review found 42 issues worth fixing on startup.network, 15 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.6 s |
| May 9, 2026 | 3.7 s |
| May 16, 2026 | 3.7 s |
| May 23, 2026 | 3.6 s |
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.7 s |
| Jun 13, 2026 | 3.8 s |
| Jun 20, 2026 | 3.7 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 3.9 s |
| Jul 11, 2026 | 3.9 s |
| Jul 18, 2026 | 3.8 s |
| Jul 25, 2026 | 3.7 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.8 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.7 s |
| Sep 5, 2026 | 3.6 s |
| Sep 12, 2026 | 3.6 s |
| Sep 19, 2026 | 3.7 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.8 s |
| Oct 10, 2026 | 3.9 s |
| Oct 17, 2026 | 4.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 161 ms |
| May 9, 2026 | 168 ms |
| May 16, 2026 | 186 ms |
| May 23, 2026 | 157 ms |
| May 30, 2026 | 207 ms |
| Jun 6, 2026 | 230 ms |
| Jun 13, 2026 | 226 ms |
| Jun 20, 2026 | 223 ms |
| Jun 27, 2026 | 206 ms |
| Jul 4, 2026 | 173 ms |
| Jul 11, 2026 | 157 ms |
| Jul 18, 2026 | 152 ms |
| Jul 25, 2026 | 149 ms |
| Aug 1, 2026 | 153 ms |
| Aug 8, 2026 | 161 ms |
| Aug 15, 2026 | 157 ms |
| Aug 22, 2026 | 154 ms |
| Aug 29, 2026 | 157 ms |
| Sep 5, 2026 | 158 ms |
| Sep 12, 2026 | 164 ms |
| Sep 19, 2026 | 173 ms |
| Oct 17, 2026 | 136 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.3 s
1.9 s
2.6 s
3.2 s
3.8 s
4.5 s
5.1 s
Speed
Reduce unused JavaScript
1.6 s · 594 KiBAbout 594 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Render-blocking requests
1.4 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
8 third-party services on the page
8 third-party services load with your homepage (clym-sdk.net, Google Tag Manager and Facebook and others), adding 1.7 MB and 967 ms of main-thread time.
Mobile performance score: 60
60/100Your mobile performance score is 60 (desktop: 66). Pages that score under 90 lose visitors before the first paint.
Improve image delivery
300 ms · 422 KiB6 images could be 422 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
clym-sdk.net adds 493 ms
493 msclym-sdk.net costs a phone 493 ms of main-thread work and 804 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.
Google Tag Manager adds 216 ms
216 msGoogle Tag Manager costs a phone 216 ms of main-thread work and 315 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.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google CDN adds 115 ms
115 msGoogle CDN costs a phone 115 ms of main-thread work and 348 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.
Use efficient cache lifetimes
150 ms · 241 KiB20 files are served with short cache lifetimes, so returning visitors download them again (241 KiB).
Reduce unused CSS
150 ms · 38 KiBAbout 38 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 168 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 4 KiB4 KiB could be saved by minifying CSS.
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need.
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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 119 ms
119 msYour server sent the HTML in 119 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 4.1 s
4.1 sReal visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.9 s
3.9 sReal visitors see the first content after 3.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.3 s
2.3 sReal visitors wait 2.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 10.6 s
10.6 sYour largest element takes 10.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Sign in/Sign up LOG IN or”.
Time to Interactive: 16.9 s
16.9 sThe page becomes fully interactive after 16.9 s. Good is under 3.8 s.
Speed Index: 8.9 s
8.9 sVisually, the page fills in at 8.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 286 ms
286 msScripts block taps and scrolling for 286 ms in total while the page loads. Good is under 200 ms.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 161 ms to 136 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.6 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 140 ms
140 msReal visitors wait 140 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.038
0.038The layout barely moves while loading (CLS 0.038, good is under 0.1).
Images and page weight
Page weight: 3.1 MB in 131 requests
3.1 MBYour homepage downloads 3.1 MB in 131 requests on a phone: scripts 1.7 MB (73), images 780 KiB (29) and fonts 555 KiB (10). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (105 KiB) is 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.
2 images below the first screen load straight away
2 images further down the page (143 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.88 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.88 g of CO₂e: 105.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
30 text elements with low contrast
30 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (23 elements)
All page content should be contained by landmarks: 23 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
12 links without text
12 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
31 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is long (94 characters)
Your title is 94 characters, so Google will cut it off around 60: “Investments. Investing and investor. Venture capital investments in startups | startup.ne…”.
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
64 internal links, 18 external
The homepage links to 64 pages on startup.network and 18 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Invest in distinguished startups, find investments for your business, involve the best professionals in your ideas”.
Canonical URL set
The canonical URL is https://startup.network/.
Structured data in place
Structured data found: Organization.
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.
XML sitemap found
Your XML sitemap is reachable at https://startup.network/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://startup.network/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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (418 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://startup.network/all-startups is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
7 pages without a meta description
https://startup.network/ask-for-a-loan, https://startup.network/loans, https://startup.network/sale, https://startup.network/events/add_event, https://startup.network/events and https://startup.network/news/add_news and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
9 pages without an H1
https://startup.network/all-startups, https://startup.network/funding, https://startup.network/projects-search, https://startup.network/ask-for-a-loan, https://startup.network/sell-business and https://startup.network/events/add_event and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://startup.network/events/add_event and https://startup.network/news/add_news have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
5 pages slow to respond
https://startup.network/all-startups, https://startup.network/loans, https://startup.network/sale, https://startup.network/en/startups and https://startup.network/en/projects took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 41 found) and read each the way a search engine does.
4 checks passed
Linked pages load
13 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://startup.network/upload/iblock/456/3.Group-23.3-en.png.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
40 of 40 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 464 words of copy
The homepage carries about 464 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Apply Program”.
3 calls to action
The homepage has 3 calls to action, for example “Apply for a loan” and “Apply Program”.
Privacy and tracking
5 cookies set on arrival
5Opening the homepage sets 5 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.
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 startup.network, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on startup.network, including 18 speed issues, 4 SEO issues and 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.