dotincorp.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user LCP: 3.4 s

  3.4 s

  Real visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

• Real-user FCP: 2.6 s

  2.6 s

  Real visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.

• Real-user TTFB: 1.7 s

  1.7 s

  Real visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.

• Largest content (LCP) held steady for real visitors

  -5%

  Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.6 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• Page weight: 21.7 MB

  21.7 MB

  Your homepage downloads 21.7 MB on a phone, 19.3 MB of it images (89%). Under 2 MB keeps phones on slow connections fast.

• 1 image over 500 KB

  ai__head-preview.png weighs 1.3 MB. On a phone connection a single image that size takes seconds.

  Elements (1)

• 5 images far larger than shown

  762 KiB

  5 images are downloaded at several times the size a phone draws them, for example ai__head-preview.png at 1,344 px wide, shown at 310 px. Resized copies would save about 762 KiB.

  Elements (5)

• 15 images in older formats

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

  Elements (5)

• 16 images below the first screen load straight away

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

  Elements (5)

• About 6.2 g of CO₂ per visit

  6.16 g

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

• 2 images without alt text

  2 images have no alt text, which hurts accessibility and image search.

  View source

• Headings skip levels

  Headings skip levels (h1 → h5), which makes the page harder to scan with a screen reader.

  View source

• No meta description

  No meta description, so Google writes its own snippet from whatever text it finds.

• Title is long (73 characters)

  Your title is 73 characters, so Google will cut it off around 60: “Dot Inc. | Tactile Braille Displays and Breaking Barriers with Technology”.

  View source

• No canonical URL

  No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

• No social preview image

  No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

• No XML sitemap

  No XML sitemap at https://www.dotincorp.com/sitemap.xml, so Google discovers your pages only by following links.

• No favicon declared

  No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

• No X (Twitter) card tag

  No twitter:card tag. X falls back to Open Graph, which is incomplete here.

• 52 internal links, 7 external

  The homepage links to 52 pages on dotincorp.com and 7 external pages.

• 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.

  View source

• 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.

• 11 pages share a title

  /en, /en/usecase, /en/company, /en/news, /en/story and /en/ir and 5 others all use the title “Dot Inc. | Tactile Braille Displays and Breaking Barriers with Techno…”. Search engines can't tell which page to show for a search, so each competes with the others.

  Elements (8)

• 10 pages without a meta description

  /en/usecase, /en/company, /en/news, /en/story, /en/ir and /en/product/module and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (8)

• 8 pages slow to respond

  /en/usecase, /en/news, /en/story, /en/ir, /en/product/module and /en/product/pad and 2 others took over 3 s to send their HTML from our server.

• 15 internal pages checked

  We fetched 15 pages linked from your homepage (of 29 found) and read each the way a search engine does.

• 29 small tap targets

  29 of 40 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

• 1 JavaScript error while loading

  1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

• No HSTS header

  No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

• 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.

• 2 redirects before the homepage

  Opening https://dotincorp.com goes through 2 redirects before the homepage loads.

• 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.

• No CAA record

  dotincorp.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

  dotincorp.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.

• Phone number is not tap-to-call

  Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

• 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 1,462 words of copy

  The homepage carries about 1,462 words of visible text.

• DMARC is monitor-only (p=none)

  DMARC is set to p=none, so mail pretending to be dotincorp.com is still delivered. Add a report address, check the reports, then move to quarantine.

• Email authentication score: 70/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.

• 4 trackers load before any consent

  4

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

• 13 cookies set on arrival

  13

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

• 22 other companies contacted

  Loading the homepage contacts 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.