Website review, no card needed
dotbeyond.it website review
Visit site (opens in a new tab)Reviewed 24 October 202627 issues · 93 checks
This review found 27 issues worth fixing on dotbeyond.it, 6 of them high impact, across 93 checks. The most urgent: fails Core Web Vitals for real visitors. 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
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.1 s |
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.3 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 657 ms |
| May 9, 2026 | 750 ms |
| May 16, 2026 | 958 ms |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.0 s |
| Jun 6, 2026 | 853 ms |
| Jun 13, 2026 | 345 ms |
| Jun 20, 2026 | 195 ms |
| Jun 27, 2026 | 174 ms |
| Jul 4, 2026 | 172 ms |
| Jul 11, 2026 | 130 ms |
| Jul 18, 2026 | 146 ms |
| Jul 25, 2026 | 151 ms |
| Aug 1, 2026 | 156 ms |
| Aug 8, 2026 | 201 ms |
| Aug 15, 2026 | 201 ms |
| Sep 26, 2026 | 226 ms |
| Oct 3, 2026 | 226 ms |
| Oct 10, 2026 | 176 ms |
| Oct 17, 2026 | 176 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.7 s
1.5 s
2.2 s
3.0 s
3.7 s
4.4 s
5.2 s
5.9 s
dotbeyond.it does not allow embedding, so this is Google's rendering of the page.
Speed
Improve image delivery
1.5 MB7 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 64
64/100Your mobile performance score is 64 (desktop: 71). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
850 ms13 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
3 third-party services on the page
3 third-party services load with your homepage (dotability.it, Vimeo and dmcultura.it), adding 3.9 MB and 324 ms of main-thread time.
Reduce unused JavaScript
300 ms · 404 KiBAbout 404 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Vimeo adds 104 ms
104 msVimeo costs a phone 104 ms of main-thread work and 3.7 MB 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 CSS
300 ms · 54 KiBAbout 54 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 90 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
78 KiB6 files are served with short cache lifetimes, so returning visitors download them again (78 KiB).
Legacy JavaScript
22 KiBPolyfills for old browsers add 22 KiB JavaScript that modern phones do not need.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 1.2 s of it running JavaScript. That is comfortably low.
Server response: 553 ms
553 msYour server sent the HTML in 553 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.
Largest Contentful Paint: 6.1 s
6.1 sYour largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We bridge the gap between reality and imagination. One dot …”. Most of its time is element render delay (3.1 s).
Speed Index: 9.1 s
9.1 sVisually, the page fills in at 9.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 12.3 s
12.3 sThe page becomes fully interactive after 12.3 s. Good is under 3.8 s.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest content (LCP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 803 ms
803 msReal visitors wait 803 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
5 checks passed
Real-user INP: 179 ms
179 msReal visitors wait 179 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Tap response (INP) got 75% faster for real visitors
-75%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 657 ms to 176 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.084
0.084The layout barely moves while loading (CLS 0.084, good is under 0.1).
Total Blocking Time: 106 ms
106 msScripts block the page for only 106 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 6.5 MB in 87 requests
6.5 MBYour homepage downloads 6.5 MB in 87 requests on a phone: other files 3.2 MB (17), images 1.9 MB (13) and scripts 1.1 MB (33). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
429 KiB3 images are downloaded at several times the size a phone draws them, for example image at 1,225 px wide, shown at 271 px. Resized copies would save about 429 KiB.
About 1.8 g of CO₂ per visit
1.83 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.83 g of CO₂e: 219.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 1 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
31 internal links, 4 external
The homepage links to 31 pages on dotbeyond.it and 4 external pages.
7 checks passed
Meta description: 124 characters
Your meta description is 124 characters: “Explore Dot Beyond: crafting immersive experiences, innovative UX/UI, and cultural storytelling to shape the digital fu…”.
One H1 headline
Your main headline reads: “When reality stops, dot.”.
Title: 48 characters
Your title is a healthy 48 characters: “Where Innovation and Creativity Meet | DotBeyond”.
Canonical URL set
The canonical URL is https://www.dotbeyond.it/.
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://www.dotbeyond.it/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.
No llms.txt
There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
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 (192 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without an H1
/company and /careers have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
/careers has 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.
1 page slow to respond
/labs took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
15 small tap targets
15 of 40 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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.
Short HSTS lifetime
HSTS is set, but max-age is 182 days; one year is the recommended minimum.
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.
Deprecated X-XSS-Protection
X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.
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 (dotbeyond.it).
Valid certificate (71 days left)
The certificate from Sectigo Limited · Sectigo RSA Organization Validation Secure Server CA verifies for dotbeyond.it and is valid for another 71 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
http:// redirects to https
http://dotbeyond.it redirects to the secure version.
HTTP/2
The server speaks HTTP/2, so browsers load many files over one connection.
All 28 links work
All 28 links checked from your homepage (24 internal, 4 external) answered without errors.
Domain and trust
No CAA record
dotbeyond.it 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.
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 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 272 words of copy
The homepage carries about 272 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “contact us” and “Learn more in our Privacy Policy”.
1 call to action
The homepage has 1 call to action, for example “CONTACT US”.
Analytics in place
Analytics detected: Matomo.
Email authentication
Email authentication score: 100/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.
3 checks passed
DMARC policy: reject
DMARC tells receivers to reject mail that fails authentication, and sends you reports.
SPF with a strict ending (-all)
An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 ip4:35.152.35.7 include:spf.protection.outlook.com include:_spf.salesforce.com include:amazonses.com -all”.
DKIM signing found
A DKIM key is published (selector “selector1” and “selector2”), so receivers can verify mail really came from you.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 cookies, 2 of them by other companies (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).
Upkeep, stack and company
No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.
Stack
- Framework
- Next.js
- Analytics
- Matomo
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on dotbeyond.it, including 16 speed issues, 1 SEO issue and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.