https://typescriptlang.org

Meta description length is not optimal

Your meta description is either too short (under 100 chars) or too long (over 165 chars). Google typically shows 100–165 characters. Too short leaves value on the table; too long gets cut off with "…".

Canonical URL is missing

Without a canonical tag, Google might index multiple versions of your page (with/without www, with/without trailing slash) and split your SEO value between them.

Open Graph image missing

When someone shares your link on Twitter or Telegram, no image appears. This cuts click-through rates by up to 3×.

Open Graph URL missing

Social platforms and crawlers have no explicit canonical sharing URL for this page. This can weaken preview consistency across channels.

Images are missing dimensions

Images without dimensions can cause layout shifts while the page loads. That hurts Core Web Vitals and makes the page feel unstable.

No structured data (JSON-LD) found

No Schema.org JSON-LD blocks were found on this page. Structured data helps Google understand your content and display rich results. It also improves AI search visibility.

No analytics tracking detected

You can't improve what you don't measure. Without analytics you have no visibility into traffic, user behavior, or conversion goals.

X-Frame-Options header missing

Your site can be embedded in an invisible iframe on another website. Attackers use this technique (called "clickjacking") to trick your users into clicking things without realising it.

X-Content-Type-Options header missing

Browsers can "sniff" your files and treat them as a different file type than intended. This can allow attackers to upload files that get executed as scripts. This header prevents that.

Referrer-Policy header missing

When visitors click a link to leave your site, their browser sends your full URL (including any private query parameters) to the destination site. A referrer policy controls what gets shared.

Content Security Policy missing

There's no policy controlling what scripts and resources your page can load. Without this, an attacker who injects any code into your page can do anything — steal cookies, redirect users, exfiltrate data.

Mixed content — HTTP resources on HTTPS page

Your HTTPS page loads some resources (images, scripts, or styles) over insecure HTTP. Browsers block or warn about this, causing parts of your page to break or display incorrectly for visitors.

Missing Permissions-Policy header

Without a Permissions-Policy header, any script on your page can access the camera, microphone, geolocation, and other sensitive browser features. This is a defence-in-depth security header that limits exposure if you get XSS.

No SPF record found

SPF tells email servers which servers are allowed to send email for your domain. Without it, anyone can send email pretending to be you, and your own emails may land in spam.

No privacy policy link found

A privacy policy link is legally required in most jurisdictions if you collect any user data. It also builds trust with visitors who want to understand how their data is handled.

No structured data (Schema.org)

AI assistants and search engines use structured data to understand what your product is. Without it, they have less reliable context.

No llms.txt file

An llms.txt file can help AI systems understand which product pages and context to prefer.

Weak brand or author entity signals

The site does not expose many signals that identify the people or organization behind it.

No content date signal found

Perplexity and Google AI Overview weight fresh content significantly higher. Without a date signal, your page may be treated as potentially outdated — reducing how often AI systems cite it in answers.

First paragraph too short for AI citation

AI systems like ChatGPT, Claude, and Perplexity extract the beginning of your page as citation passages. A short or absent opening paragraph means they have little useful content to cite, reducing how often your page appears in AI answers.

Form inputs missing labels

Some form fields have no label. Screen reader users cannot tell what the field is for. Placeholder text is not a substitute — it disappears when you start typing.

Buttons without accessible label

Some buttons (icon buttons, hamburger menus, close buttons) have no accessible name. Screen readers will say "button" with no context — users cannot tell what clicking the button does.