Website review, no card needed
dreamit.com website review
Visit site (opens in a new tab)Reviewed 25 October 202625 issues · 90 checks
This review found 25 issues worth fixing on dreamit.com, 4 of them high impact, across 90 checks. The most urgent: render-blocking requests. 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
86BClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
2.4 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.
Mobile performance score: 82
82/100Your mobile performance score is 82 (desktop: 98). Pages that score under 90 lose visitors before the first paint.
Improve image delivery
450 ms · 416 KiB15 images could be 416 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 420 KiB26 files are served with short cache lifetimes, so returning visitors download them again (420 KiB).
8 third-party services on the page
8 third-party services load with your homepage (website-files.com, Facebook and Hubspot and others), adding 1.1 MB and 379 ms of main-thread time.
website-files.com adds 180 ms
180 mswebsite-files.com costs a phone 180 ms of main-thread work and 794 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.
Reduce unused JavaScript
150 ms · 146 KiBAbout 146 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 79 ms. During a long task the page ignores taps.
Legacy JavaScript
26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need.
Reduce unused CSS
17 KiBAbout 17 KiB of CSS is downloaded but never applied on this page.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 481 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
96 images without width and height
96 images have no width and height attributes, so the layout jumps as each one loads.
Largest Contentful Paint: 3.9 s
3.9 sYour largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Investing in Transformative Early-Stage Cybersecurity Start…”.
Time to Interactive: 6.5 s
6.5 sThe page becomes fully interactive after 6.5 s. Good is under 3.8 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
3 checks passed
Speed Index: 3.2 s
3.2 sVisually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 22 ms
22 msScripts block the page for only 22 ms while loading. Good is under 200 ms.
Images and page weight
An image on the first screen is lazy-loaded
6a9197ac0b97020c96543f49_6a68ccd90cfc9036365655b3_acsense.pn is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image far larger than shown
48 KiB1 image is downloaded at several times the size a phone draws it, for example 6a9197ac0b97020c96543f49_6a68ccd90cfc9036365655b3_acsense.pn at 1,872 px wide, shown at 285 px. Resized copies would save about 48 KiB.
4 images in older formats
4 images (184 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 0.3 g of CO₂ per visit
0.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.32 g of CO₂e: 38.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.1 MB in 51 requests
1.1 MBYour homepage downloads 1.1 MB in 51 requests on a phone: scripts 542 KiB (18), images 541 KiB (22) and fonts 54 KiB (2). That is a lean page.
Accessibility
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail 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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 96 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (186 characters)
Your meta description is 186 characters; Google truncates after about 160, so the end of your pitch is cut.
18 internal links, 2 external
The homepage links to 18 pages on dreamit.com and 2 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Investing in Transformative Early-Stage Cybersecurity Startups”.
Title: 53 characters
Your title is a healthy 53 characters: “Dreamit Ventures | Early-Stage Cybersecurity Investor”.
Canonical URL set
The canonical URL is https://dreamit.com/.
Structured data in place
Structured data found: WebPage.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://dreamit.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
3 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 (243 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes /llms.txt (2 KiB, 13 links), a plain-text guide to the site for AI tools.
Other pages
6 pages without a meta description
/events/cyber-innovation-conference-2026, /investor-network, /customer-sprints, /advisors, /newsletter and /brand-assets have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages with very little text
/events/cyber-innovation-conference-2026 and /brand-assets 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.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 13 pages we checked loaded without an error.
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 an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Security and trust
No Content-Security-Policy
No Content-Security-Policy header, the main browser-side defence against injected scripts.
No clickjacking protection
Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.
No X-Content-Type-Options
X-Content-Type-Options: nosniff is missing, so browsers may guess file types.
No Referrer-Policy
No Referrer-Policy header, so full URLs can leak to the sites you link to.
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
6 checks passed
Served over HTTPS
The homepage is served over HTTPS (dreamit.com).
Valid certificate (63 days left)
The certificate from Google Trust Services · WE1 verifies for dreamit.com and is valid for another 63 days.
HSTS enabled
Strict-Transport-Security is set, so browsers always use https.
http:// redirects to https
http://dreamit.com redirects to the secure version.
HTTP/2 and HTTP/3
The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.
All 16 links work
All 16 links checked from your homepage (14 internal, 2 external) answered without errors.
Domain and trust
No CAA record
dreamit.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
DNSSEC is off
dreamit.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.
2 checks passed
Domain is 32 years old
32 yearsdreamit.com was registered in Sep 1994 through Name.com, Inc.. An established domain carries more trust with email providers and search engines.
Registered until Sep 2032
dreamit.com is registered until Sep 2032.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Thin social proof
Social proof on the homepage: “350+ companies”. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
Only about 236 words
The homepage has only about 236 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Join Our Investor Network”, “Join Our Customer Network” and “Sign Up For Our Newsletters”.
Analytics in place
Analytics detected: HubSpot.
Email authentication
DMARC is monitor-only (p=none)
DMARC is set to p=none, so mail pretending to be dreamit.com is still delivered. Add a report address, check the reports, then move to quarantine.
Email authentication score: 75/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
2 checks passed
SPF with a strict ending (-all)
An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 include:3336916.spf02.hubspotemail.net -all”.
DKIM signing found
A DKIM key is published (selector “google” and “hs1”), so receivers can verify mail really came from you.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads HubSpot, LinkedIn Insight and Meta Pixel (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
18 other companies contacted
Loading the homepage contacts 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) loads with the page.
Upkeep, stack and company
No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.
Stack
- CMS
- Webflow
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on dreamit.com, including 10 speed issues, 1 SEO issue and 4 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.