Skip to main content
Archived

SEO Report for https://angbad88.net

Your general SEO Checkup Score


SEO Score69/100
Average SEO score of top 100 sites: 75%This value indicates the average SEO score of the top 100 most visited websites in the US (in the past 12 months)
AI Visibility47/100
AI visibility score reflects brand reach in AI

Your site scored 69/100, below the 75 average for top sites. We found 13 issues to fix, and clearing them is how you move up. And an AI Visibility Score of 47/100 means ChatGPT, Gemini and Perplexity mention your brand only occasionally, which is ground your competitors are leaving open.

13 Failed
7 Warnings
43 Passed

Want to fix these issues and track your progress?

Issues to fix

HIGH
To improve the website experience for your visitors, it is recommended to eliminate any render-blocking resources on this webpage.
Details
HIGH
Users may abandon pages that take longer than 5 seconds to load, resulting in a potential loss of up to 50% of visitors. Faster loading pages can lead to increased traffic, better conversions, and higher sales.
Details
HIGH
Use the page's main keyword in the title tag, the meta description and at least one H1 or H2 heading.
Details
HIGH
Using images in a modern format can significantly reduce the file size and improve the loading speed of a webpage, providing a better user experience and potentially increasing engagement.
Details
MEDIUM
Resize oversized images to the dimensions at which the page displays them, or offer several sizes through responsive images.
Details
MEDIUM
By creating a custom 404 error page with helpful links and information, users are more likely to stay on the site and continue to explore.
Details
MEDIUM
To provide a good user experience, Google recommends that sites should aim for a First Contentful Paint value of 1.8 seconds or less.
Details
MEDIUM
Avoid performance and security issues by adding "rel=noopener" or "rel=noreferrer" to your "target=_blank" links.
Details
LOW
Fix the console errors that Chrome logged for the page, as anything that fails to load may also be missing from the version Google indexes.
Details
LOW
While a canonical link tag can help in resolving duplicate content issues, it's important to verify that the specified URL is accurate, especially if the site's URL structure has been recently updated.
Details
LOW
Without an SPF record, spammers can easily spoof emails from this domain, potentially leading to compromised email security and deliverability issues.
Details
LOW
Using more than 20 HTTP requests on a webpage can negatively impact the loading time.
Details

AI Insights

Score:0
Failed:0
Warnings:0
Passed:5
Domain Business Context
Understanding the business context of a domain can help you create content that is more relevant to your target audience and differentiate your website from competitors.

What is this domain about

Online gambling and betting promotional homepage for AD88, covering casino, sports betting, slots, lottery, and registration offers.

Industry Niche

Online Gambling Promotions

Target Audience

Adults interested in online betting, casino games, promotions, and account sign-up guidance.

This test will check the business context of the domain associated with the analyzed webpage. The business context includes the domain's description, target audience and industry niche (if applicable). Understanding the business context of a domain can help you create content that is more relevant to your target audience and differentiate your website from competitors.
LLM Visibility Checker
LLM Visibility Checker

Track your brand across ChatGPT, Gemini and Claude

Get an AI Presence Score, see which of your pages get cited, and follow how you compare with competitors over time.

How visible your brand is to AI engines
Content Strengths and Weaknesses

This webpage is highly promotional and covers a broad set of gambling products, bonuses, and onboarding steps in a clear, sales-oriented structure. However, it relies heavily on marketing claims and lacks independent evidence, author transparency, or substantive editorial depth.

Content Strengths

  • Clear Promotional Structure
  • Broad Product Coverage
  • Action-Oriented Guidance

Content Weaknesses

  • Weak Evidence Base
  • Overly Promotional Tone
  • Limited Editorial Depth
This test will analyze the content of the webpage to identify its strengths and weaknesses. The analysis includes factors such as keyword usage, readability, originality, and relevance to the target audience. By understanding the strengths and weaknesses of your content, you can make informed decisions about how to improve it and better meet the needs of your audience.
Content Trust
42%
Topical Relevance95%
Subject Expertise48%
Credibility30%

This webpage is topically focused on online gambling and mostly stays on that theme, but its trustworthiness is weakened by unsupported claims and limited transparency. It presents policy links and a copyright notice, yet it lacks visible author attribution, company details, contact information, and third-party verification on the page.

This test will evaluate the trustworthiness of the content on the webpage. It assesses factors such as the credibility of sources, accuracy of information, and overall reliability. A high level of content trust can enhance your website's reputation and improve its ranking in search engine results.
Visual SEO Analysis
Visual SEO Analysis

Find out if your page design converts the visitors you earn

We score six things that decide whether a visitor stays and acts, from the first screen to the path to action, and rank every fix by effort and impact.

How your page's design and UX affect conversions
Content Freshness
62%

The page appears current in a superficial sense because it references 2026, includes a 2026 copyright, and mentions recent member-count and ranking claims. However, there are no explicit publish or update timestamps on the main content, so freshness is supported mainly by contextual and boilerplate signals rather than primary dating evidence.

Positive Signals

  • 2026 copyright notice
  • Recent 2026 claims
  • Current-year promotional language

Staleness Signals

  • No publish date shown
  • No visible update timestamp
This test will check the freshness of the content on the webpage. It evaluates how recently the content was created or updated, and whether it remains relevant to current trends and user interests. Fresh content can attract more visitors and improve your website's ranking in search engine results.
Content Opportunities

The page already covers the basics of brand positioning, products, promotions, and registration, but it leaves major gaps in proof, transparency, and user education. The biggest opportunities are to add verifiable trust assets, deeper product guidance, and more practical help content that answers user intent beyond promotion.

Quick Wins

  • •Add a visible support email and phone number in the footer or contact area.
  • •Link each claimed license or certification to a verifiable source or certificate page.
  • •Expand the FAQ with withdrawal, verification, and bonus-rule questions that are not currently answered.
This test will identify potential content opportunities for the webpage. It analyzes the current content landscape, identifies gaps in coverage, and suggests topics or keywords that could be targeted to attract more visitors and improve search engine rankings.

Common SEO issues

Score:70
Failed:3
Warnings:3
Passed:13
Meta Title Test
100% of top 100 sites passed
This webpage is using a title tag with a length of 73 characters. Long titles can blur the main topic of the page and get cut off in search results and AI citations. Put the most important words first. We recommend a title between 20 and 60 characters, so it shows in full in search results on both phones and desktop.
Text: AD88 GIFTCARD 🏆 Trang Chủ AD88.Com Uy Tín Chính Thức 2026 Nhận Ngay +888k
Length: 73 characters
The meta title is an HTML element that defines a page's title, displayed in search engine results, browser tabs, and bookmark lists. A concise, keyword-relevant title is a strong on-page ranking signal and a major driver of organic click-through rate. AI answer engines and LLM-driven search experiences also rely on the title to identify, summarize, and cite the page in generative results.
Meta Description Test
92% of top 100 sites passed
This webpage is using a meta description tag with a length of 203 characters. Long descriptions get cut off in search results, and the cut can hide key details from both people and AI assistants that build answers from those results. We recommend a description between 70 and 160 characters (spaces included), with the most important information first.
Text: AD88 là nền tảng giải trí trực tuyến top #1 Châu Á với đa dạng trò chơi như game bài, thể thao, tài xỉu, nổ hũ. Hỗ trợ Android, iOS cùng hệ thống nạp rút tiện lợi và nhiều ưu đãi dành cho thành viên mới.
Length: 203 characters
The meta description is an HTML tag that provides a short summary of a page's content, often shown beneath the title in search results. While not a direct ranking factor, an accurate and inviting description significantly improves click-through rate from organic listings. AI answer engines and social platforms also use it as a trusted summary when generating previews, citations and shareable snippets.
Google Search Results Preview Test
Desktop version
https://mygiftcardsite.caiqueparrots.com/AD88 GIFTCARD 🏆 Trang Chủ AD88.Com Uy Tín Chính Thức 2026 Nhận Ngay +888kAD88 là nền tảng giải trí trực tuyến top #1 Châu Á với đa dạng trò chơi như game bài, thể thao, tài xỉu, nổ hũ. Hỗ trợ Android, iOS cùng hệ thống nạp rút tiện lợi và nhiều ưu đãi dành cho thành viên mới.
Mobile version
https://mygiftcardsite.caiqueparrots.com/AD88 GIFTCARD 🏆 Trang Chủ AD88.Com Uy Tín Chính Thức 2026 Nhận Ngay +888kAD88 là nền tảng giải trí trực tuyến top #1 Châu Á với đa dạng trò chơi như game bài, thể thao, tài xỉu, nổ hũ. Hỗ trợ Android, iOS cùng hệ thống nạp rút tiện lợi và nhiều ưu đãi dành cho thành viên mới.
A simulated preview of how the page may appear in Google search results, combining the title, URL, and meta description as Google typically renders them. Useful for spotting truncated text, weak phrasing, or missing elements before publishing, since the snippet directly influences whether searchers click through.
Social Media Meta Tags Test
89% of top 100 sites passed
This webpage is using social media meta tags, but it is missing these required Open Graph properties: og:url. Social networks and messaging apps rely on these properties to build accurate link previews, and when they're missing, the platforms fill in the gaps on their own, which may not match how the page should appear. We recommend adding the missing properties.
Open Graph Meta Tags
og:localevi_VN
og:typewebsite
og:titleAD88 GIFTCARD 🏆 Trang Chủ AD88.Com Uy Tín Chính Thức 2026 Nhận Ngay +888k
og:descriptionAD88 là nền tảng giải trí trực tuyến top #1 Châu Á với đa dạng trò chơi như game bài, thể thao, tài xỉu, nổ hũ. Hỗ trợ Android, iOS cùng hệ thống nạp rút tiện lợi và nhiều ưu đãi dành cho thành viên mới.
og:site_namehttps://mygiftcardsite.caiqueparrots.com
og:updated_time2026-11-17T09:15:41+07:00
og:imagehttps://mygiftcardsite.caiqueparrots.com/wp-content/uploads/2026/11/ad88-giai-ma-thuong-hieu-ca-cuoc-xanh-chin-hang-dau-2026.webp
og:image:secure_urlhttps://mygiftcardsite.caiqueparrots.com/wp-content/uploads/2026/11/ad88-giai-ma-thuong-hieu-ca-cuoc-xanh-chin-hang-dau-2026.webp
og:image:width800
og:image:height400
og:image:altAD88 mang đến sân chơi casino thời thượng cho những ai mong muốn đấu trí săn thưởng khủng. Khám phá thương hiệu để có hành trang vững chắc trước khi tham gia.
og:image:typeimage/webp
Twitter Card Meta Tags
twitter:cardsummary_large_image
twitter:titleAD88 GIFTCARD 🏆 Trang Chủ AD88.Com Uy Tín Chính Thức 2026 Nhận Ngay +888k
twitter:descriptionAD88 là nền tảng giải trí trực tuyến top #1 Châu Á với đa dạng trò chơi như game bài, thể thao, tài xỉu, nổ hũ. Hỗ trợ Android, iOS cùng hệ thống nạp rút tiện lợi và nhiều ưu đãi dành cho thành viên mới.
twitter:site@admin
twitter:creator@admin
twitter:imagehttps://mygiftcardsite.caiqueparrots.com/wp-content/uploads/2026/11/ad88-giai-ma-thuong-hieu-ca-cuoc-xanh-chin-hang-dau-2026.webp
twitter:label1Được viết bởi
twitter:data1admin
twitter:label2Thời gian để đọc
twitter:data214 phút
Open Graph and Twitter Card meta tags tell social platforms and link unfurlers how to display a page when its URL is shared. Well-formed tags produce richer previews with the intended title, description, and image, which improves click-through on social channels. They also serve as a structured signal that AI crawlers and answer engines can use when summarizing the page.
Most Common Keywords Test
There's no ideal keyword density (search engines look at meaning, not just word counts, and treat keyword stuffing as spam). The most common keywords should, however, reflect the page's main topic, not repeated text such as menus or button labels. Clear, natural writing helps search engines and AI assistants understand the page and quote it accurately.
36được
31những
25thành
25không
24người
A frequency analysis of the most repeated words and phrases in the page's visible content. Useful for getting a quick sense of which topics search engines are likely to associate with the page, and for spotting cases where the actual content drifts from the intended subject.
Keywords Usage Test
48% of top 100 sites passed
None of this webpage's most common keywords appears in all three key places: the title, the meta description and the headings! When these elements don't share the main terms of the text, search engines and AI assistants get a less consistent picture of what the page is about.
Keyword
Title tag
Meta description
Headings
được
những
thành
không
người
Cross-checks whether the most frequently used keywords on the page also appear in the title and meta description. Alignment between body content and metadata helps search engines confirm the page's topic and reinforces relevance for those terms.
Keywords Cloud Test
bước
casino
chính
chúng
chơi
chưa
chất
chứng
cung
công
cùng
cũng
cược
danh
dùng
dưới
dịch
game
giao
giúp
giải
hiện
hiệu
hoạt
hàng
hành
khoản
khác
không
kiểm
kiện
liên
loại
lượng
minh
muốn
mình
mệnh
ngay
nghiệm
ngoài
ngày
người
nhanh
nhiều
nhuận
nhất
nhận
nhập
những
năng
phát
phép
phẩm
quốc
siêu
sách
tham
thao
thiết
thuận
thành
thích
thông
thương
thưởng
thật
thống
thời
thức
thực
tiên
tiêu
tiếp
tiền
toàn
trang
triển
trong
truy
trên
trình
trước
trường
trải
tích
tính
tượng
tảng
viên
việc
đang
điều
điểm
đông
đăng
được
định
đồng
động
A visual word cloud of the page's content, with more frequent terms shown in larger text. Provides a quick at-a-glance view of which words dominate the page, helping confirm that the visible content reflects the intended topic.
Competitor Domains Test
Competitor Domains

Understand your competitors' SEO and backlink profile

Get related competitors and their domain authority score in relation to your domain.

Identifies up to ten domains that compete for similar organic search results, ranked by overall domain authority based on the volume and quality of their backlink profiles. Useful for benchmarking the competitive landscape and prioritizing which sites to study for content and link-building strategy.
Heading Tags Test
62% of top 100 sites passed
This webpage contains heading tags. Clear headings help search engines and AI assistants understand how the content is organized and find the right section of the page. Each heading works as a label for the text under it, which makes a single section easier to quote in search results and AI answers.
H1 tags
AD88 GIFTCARD Trang Chủ AD88.Com Uy Tín Chính Thức 2026 Nhận Ngay +888k
H2 tags
Sứ mệnh phát triển cùng mục tiêu hoạt động
Những giấy phép chất lượng mà AD88 đã đạt được
Ưu điểm giúp nhà cái thu hút lượng người truy cập lớn
Danh mục các sản phẩm nổi bật chỉ có tại AD88
Điểm qua kho ưu đãi độc quyền mà AD88 cung cấp
Hướng dẫn đăng ký AD88 tất tần tật từ A – Z
Quy trình nạp tiền chuẩn cho ai mới tham gia
FAQ – Câu hỏi thường gặp
Kết luận
Inspects the page for H1 and H2 heading tags and reports their structure. Headings give both users and search engines a clear outline of the page's topics, with the H1 acting as the primary subject and H2s framing major sections. A clean heading hierarchy also helps AI answer engines segment the content into discrete passages they can quote or summarize.
Robots.txt Test
99% of top 100 sites passed
This website is using a robots.txt file.
Verifies whether the site exposes a robots.txt file at the root domain. This file is the first resource most crawlers request, telling search engines and other bots which paths they may or may not access. It is also the standard mechanism for allowing or blocking modern AI crawlers used by training pipelines and answer engines.
Sitemap Test
83% of top 100 sites passed
Looks for an XML sitemap on the site and reports whether one is published. Sitemaps give search engines an explicit, machine-readable list of the URLs you want crawled, along with metadata such as last-modified dates, which speeds up discovery of new and updated pages. They are especially useful for large sites or those with weak internal linking.
Image Alt Test
78% of top 100 sites passed
All images on this webpage have alt text. Search engines and AI assistants understand a page mainly through its text, and the alt text is the part that describes each image. People who use screen readers hear the same text in place of the image.
Inspects whether images on the page include descriptive alt attributes. Alt text provides accessibility for screen readers, a fallback when images fail to load, and a textual signal that helps search engines understand image content. It also improves how AI crawlers and image search tools interpret and surface the visuals.
Responsive Image Test
29% of top 100 sites passed
This webpage uses oversized images, larger than the size at which the page displays them! The browser downloads each one at full size and shrinks it on screen, and the extra pixels cost bandwidth and loading time without ever being seen. Slow-loading images hold back the Core Web Vitals that Google's ranking systems take into account, and they make visitors wait. Resizing each image to the dimensions at which it is shown, or offering several sizes through responsive images, removes that waste and speeds up the page for everyone.

Responsive Image Test

How to pass this test?

This test fails when one or more images on the page are served at dimensions significantly larger than the size at which the browser actually renders them. Fixing this issue means resizing the source files (or serving responsive variants) so the bytes downloaded match the pixels actually displayed. The result is faster page loads, lower data usage, and better Core Web Vitals scores.

Example

<img
  src="/images/hero-800.jpg"
  srcset="/images/hero-400.jpg 400w,
          /images/hero-800.jpg 800w,
          /images/hero-1600.jpg 1600w"
  sizes="(max-width: 640px) 100vw, 800px"
  alt="Marathon runners at sunrise"
  width="800" height="450">

Where to make the change

  • Raw HTML: use srcset and sizes to let the browser pick the right variant for the user's viewport. Always include intrinsic width and height attributes.
  • WordPress: WordPress generates multiple image sizes automatically. Use the the_post_thumbnail() helper or the block editor's image block, both of which emit responsive srcset markup.
  • Shopify: use the image_url Liquid filter with size parameters (for example {{ image | image_url: width: 800 }}) and pair with image_tag to emit a responsive image.
  • Wix or Squarespace: both platforms generate responsive variants automatically; this issue is typically caused by uploading a deliberately oversized image.
  • Headless or framework sites: use the framework's image component (for example next/image or astro:assets), which generates responsive variants and lazy-loads off-screen images.

Common causes and how to resolve them

  • Original camera or stock-photo file uploaded as-is: a 6000-pixel-wide JPEG rendered in a 400-pixel column wastes most of the bytes. Resize the source or generate responsive variants.
  • No srcset: the browser has no choice but to use the single source. Add multiple variants so mobile users get smaller files.
  • Hero images sized for ultra-wide displays: if your largest layout is 1600 pixels, do not ship a 4000-pixel original.
  • Background images set in CSS without responsive sources: use the image-set() CSS function or media queries to swap in different image files at different breakpoints.

Best practices

  • Generate variants at common widths: 400, 800, 1200, and 1600 pixels covers most viewports cleanly.
  • Always set width and height: intrinsic dimensions let the browser reserve space and avoid layout shift, helping CLS.
  • Lazy-load off-screen images: add loading="lazy" to images below the fold so the browser only downloads them when needed.
  • Pair with modern formats: resizing alone is good; resizing and serving WebP or AVIF compounds the savings.
Compares the natural dimensions of each image to the size at which it is actually rendered in the user's viewport. Serving images significantly larger than needed wastes bandwidth, slows page load, and forces the browser to scale assets unnecessarily, all of which hurt performance and user experience.
Image Aspect Ratio Test
75% of top 100 sites passed
All images on this webpage are displayed at their natural aspect ratio. Correctly proportioned images keep the page looking polished and trustworthy.
Compares each image's natural aspect ratio against the ratio at which it is displayed on the page. Significant mismatches result in stretched or squashed visuals that look unprofessional and degrade the user experience.
Deprecated HTML Tags Test
94% of top 100 sites passed
The HTML of this webpage is free of deprecated tags, which helps the page render consistently across browsers and devices.
Scans the markup for HTML elements that are no longer part of the modern HTML specification. Deprecated tags may still render today, but browsers can drop support at any time, leading to broken layouts and rendering inconsistencies. Replacing them with current standards keeps the page resilient and easier to maintain.
Google Analytics Test
72% of top 100 sites passed
This webpage uses Google Analytics, which tracks where visitors come from and how they move through the site, from first engagement to conversion. Visits sent by AI assistants such as ChatGPT and Perplexity show up in its reports as their own traffic sources.
Detects whether the page is instrumented with Google Analytics tracking code. Analytics is not an SEO ranking factor, but having reliable traffic and behavior data is essential for measuring the impact of SEO work and identifying opportunities for improvement.
Favicon Test
100% of top 100 sites passed
favicon
This website has a favicon, the small icon that stands for the site in browser tabs and bookmarks. It also appears next to the site's links in Google search results and in the answers of AI assistants, helping people recognize the site at a glance.
Verifies whether the site declares a favicon and that it loads correctly. Favicons appear in browser tabs, bookmarks, and increasingly in search engine result pages, where they reinforce brand recognition and make a listing easier to spot at a glance.
JS Error Test
83% of top 100 sites passed
No JavaScript errors interrupted this webpage's scripts while it loaded. Visitors aren't the only ones who need those scripts to run: Google runs a page's JavaScript before indexing it, and AI agents now click buttons and fill in forms to complete tasks for their users.
Inspects the page for JavaScript runtime errors that occur as it loads. Unhandled errors can break interactive features, leave content unrendered, and signal poor code quality, all of which hurt the user experience that search engines factor into rankings.
Console Errors Test
27% of top 100 sites passed
Chrome's console showed errors while this webpage loaded. Console errors usually mean that a file failed to load or that the browser had to block a request. Google renders pages with the same engine, and the version it indexes for its search results and AI Overviews may lack whatever didn't load.

Console Errors Test

How to pass this test?

Console errors include any unhandled JavaScript exceptions, network request failures, security warnings, or deprecation notices the browser emits while loading the page. Fixing this issue means resolving the underlying problem each error reports rather than suppressing the message. Even errors that do not visibly break the page can degrade performance, leak data, or trip Core Web Vitals.

Where to make the change

  • Open DevTools, Console tab: expand each entry to see the file, line, and stack trace. Right-click an entry to filter, save, or jump to the source.
  • Application code: patch the offending script (see js-errors). For network failures, fix the failing endpoint or remove the stale request.
  • Third-party tags: if the error originates in an analytics, ad, or widget script, update the snippet, switch to the vendor's current loader, or remove unused tags.

Common causes and how to resolve them

  • JavaScript runtime errors: see the JS Error Test fix; the same approach applies.
  • Failed network requests (404 or 5xx): remove the dead request or fix the endpoint. Stale tracking pixels and removed assets are common culprits.
  • Mixed content warnings: the page is HTTPS but loads an HTTP resource. Update the resource URL to https://.
  • CORS or CSP violations: tighten or expand the policy as appropriate. CSP errors usually require allowlisting the offending origin in the response header.
  • Deprecation warnings: update the call site to use the recommended API. These do not break the page today but will when the deprecation cycle completes.

Best practices

  • Treat the console as a build artifact: a clean console is a sign of a healthy page. Aim for zero errors and zero warnings on production routes.
  • Use error monitoring in production: real users hit edge cases your local environment will never reproduce. A monitoring service surfaces them with frequency data.
  • Defer or remove unused third-party scripts: every removed script is one fewer source of console noise.
Reviews the browser console for warnings and errors emitted while the page loads. Console messages often expose underlying issues such as failed network requests, deprecated APIs, or security warnings that can quietly degrade the experience even when the page appears to work.
Charset Declaration Test
96% of top 100 sites passed
This webpage declares its character encoding. Browsers, search engines and AI crawlers can read its text correctly without having to guess which encoding it uses.
Content-Type: text/html; charset=UTF-8
Checks whether the page declares a character encoding such as UTF-8. Without an explicit charset declaration, browsers must guess the encoding, which can lead to garbled symbols, broken accented characters, and inconsistent rendering across devices. UTF-8 is the modern standard recommended by Google.

Speed optimizations

Score:62
Failed:5
Warnings:3
Passed:12
HTML Page Size Test
23% of top 100 sites passed
The size of this webpage's HTML is 23.18 Kb and is under the average webpage's HTML size of 33 Kb. Faster loading websites result in a better user experience, higher conversion rates, and generally better search engine rankings.
Measures the size of the raw HTML document, excluding images and external CSS or JavaScript. Bloated HTML increases time to first byte and parsing time, slowing down rendering on mobile networks and lower-powered devices. Trimming inline styles, redundant markup, and oversized inline data keeps initial load fast.
DOM Size Test
56% of top 100 sites passed
The Document Object Model (DOM) of this webpage has 479 nodes which is less than the recommended value of 1,500 nodes.
Measures the size and depth of the page's Document Object Model, the tree of nodes the browser builds from the HTML. Very large DOMs increase memory usage, lengthen style and layout calculations, and slow down rendering, particularly on mobile devices. Keeping the DOM lean improves both load time and runtime responsiveness.
HTML Compression/GZIP Test
99% of top 100 sites passed
This webpage is successfully compressed using zstd compression on your code. The HTML code is compressed from 86.86 Kb to 23.18 Kb (73% size savings). This helps ensure a faster loading webpage and improved user experience.
Verifies whether the server delivers the HTML using a compression algorithm such as Gzip or Brotli. Compressed responses dramatically reduce transfer size with negligible decompression cost, translating directly into faster page loads, especially on slower connections.
Site Loading Speed Test
71% of top 100 sites passed
The loading time of this webpage (measured from N. Virginia, US) is around 11.73 seconds and is greater than the average loading speed which is 5 seconds!
Related Keywords

Accurate historical loading speed monitor and reports

Get detailed and accurate loading speed reports for your websites and see how your pages are being loaded over time.

Measures the overall time required to load the page in the browser. Page speed is a confirmed Google ranking factor and a strong driver of bounce rate, with slower pages losing a meaningful share of users before they even see the content. Faster pages also tend to convert better, making this a key metric for both SEO and revenue.
JS Execution Time Test
53% of top 100 sites passed
The JavaScript code used by this webpage is executed in less than 2 seconds.
Reports the total time the browser spends parsing, compiling, and executing JavaScript while the page loads. Heavy JavaScript work blocks the main thread and is the primary cause of poor Interaction to Next Paint, the Core Web Vital that replaced First Input Delay in 2024 and that Google uses as part of its ranking algorithms. Reducing bundle size and deferring non-critical scripts directly improves perceived performance.
Page Objects Test
7% of top 100 sites passed
This webpage is using more than 20 http requests, which can slow down page loading and negatively impact user experience!
Content size by content type
Content type
Percent
Size
image
98.5 %
26.02 Mb
javascript
1.2 %
328.26 Kb
css
0.1 %
31.25 Kb
html
0.1 %
25.72 Kb
font
0.0 %
7.87 Kb
other
0.0 %
481 B
TOTAL
100%
26.41 Mb
Requests by content type
Content type
Percent
Requests
javascript
48.1 %
13
image
29.6 %
8
html
7.4 %
2
css
7.4 %
2
font
3.7 %
1
other
3.7 %
1
TOTAL
100%
27
Content size by domain
Domain
Percent
Size
mygiftcardsite.caiqueparrots.com
99.1 %
26.18 Mb
googletagmanager.com
0.7 %
177.38 Kb
ajax.googleapis.com
0.1 %
30.91 Kb
website-analytics.net
0.0 %
10.48 Kb
static.cloudflareinsights.com
0.0 %
10.23 Kb
s.w.org
0.0 %
1.04 Kb
TOTAL
100%
26.41 Mb
Requests by domain
Domain
Percent
Requests
mygiftcardsite.caiqueparrots.com
81.5 %
22
googletagmanager.com
3.7 %
1
website-analytics.net
3.7 %
1
static.cloudflareinsights.com
3.7 %
1
ajax.googleapis.com
3.7 %
1
s.w.org
3.7 %
1
TOTAL
100%
27
Verifies that every resource the page requests, including images, scripts, stylesheets, and fonts, can be successfully retrieved. Broken or unreachable assets can leave the page rendered incorrectly, trigger console errors, and damage both user experience and how search engines perceive page quality.
CDN Usage Test
95% of top 100 sites passed
This webpage is serving all images, javascript and css resources from CDNs.
Detects whether static assets such as images, JavaScript, and CSS are delivered through a Content Delivery Network. CDNs serve files from edge locations close to the user, reducing latency, improving cache hit rates, and offloading traffic from the origin server. The result is faster, more consistent page performance worldwide.
Modern Image Format Test
43% of top 100 sites passed
This webpage is not serving images in a modern format! Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.

Modern Image Format Test

How to pass this test?

This test fails when images are served in legacy formats such as JPEG and PNG instead of modern alternatives like WebP or AVIF. Modern formats compress significantly better at equivalent visual quality, which means smaller transfers, faster page loads, and lower data usage for visitors on metered connections. Fixing this issue means generating modern variants and serving them to browsers that support them.

Example

<picture>
  <source srcset="/images/hero.avif" type="image/avif">
  <source srcset="/images/hero.webp" type="image/webp">
  <img src="/images/hero.jpg" alt="Marathon runners at sunrise" width="1600" height="900">
</picture>

Where to make the change

  • Raw HTML: use the <picture> element with multiple <source> entries so the browser picks the best supported format.
  • WordPress: WordPress 6.x and later supports WebP natively. Use a media optimization plugin to convert existing JPEGs and PNGs and serve modern formats automatically.
  • Shopify: Shopify's image CDN can serve WebP automatically; using the image_url filter with format parameter or the image_tag helper handles negotiation.
  • Wix or Squarespace: both platforms convert and serve WebP automatically when supported by the visitor's browser.
  • Headless or framework sites: components like next/image and astro:assets generate AVIF and WebP variants at build time and serve the best format per request.

Common causes and how to resolve them

  • Only legacy formats published: add a build step or image CDN that generates WebP and AVIF alongside the original.
  • Single-format <img> tag: wrap the image in <picture> with <source> entries for AVIF and WebP, falling back to the JPEG.
  • Image CDN not negotiating format: enable automatic format conversion or pass a format=auto query parameter (depends on provider).
  • SVG used where a raster image would be smaller (or vice versa): illustrations and icons should be SVG; photos should be raster in a modern format. Mixing them up wastes bytes.

Best practices

  • AVIF first, WebP fallback, JPEG last: AVIF compresses best, WebP is widely supported, JPEG remains the universal fallback.
  • Match quality to use case: hero images can use higher quality settings; thumbnails can drop quality without visible loss.
  • Use an image CDN: services like Cloudflare Images, Cloudinary, or Imgix handle resizing, format conversion, and caching in one step.
Identifies images served in legacy formats such as JPEG and PNG instead of modern alternatives like WebP or AVIF. Modern formats compress significantly better at equivalent visual quality, which means smaller transfers, faster page loads, and lower data usage for visitors on metered connections.
Image Metadata Test
72% of top 100 sites passed
This webpage is not using images with large metadata.
Flags images carrying disproportionately large embedded metadata such as EXIF data, thumbnails, color profiles, geolocation, and camera information. This metadata is rarely useful on the web and adds bytes to every request without any rendering benefit, making it an easy win for shrinking image payloads.
Image Caching Test
95% of top 100 sites passed
This website is using cache headers for images and the browsers will display these images from the cache.
Inspects whether image responses include caching headers that allow browsers to store them for repeat visits. With proper caching directives, returning visitors retrieve images from the local cache instead of refetching them, producing noticeably faster subsequent page loads.
JavaScript Caching Test
96% of top 100 sites passed
This webpage is using cache headers for all JavaScript resources.
Inspects whether external JavaScript files are served with caching headers that allow browsers to store and reuse them. Cached scripts skip the network on repeat visits, reducing load time and bandwidth for returning users without sacrificing the ability to push fresh code by versioning file URLs.
CSS Caching Test
98% of top 100 sites passed
This webpage is using cache headers for all CSS resources.
Inspects whether external CSS files are served with caching headers that allow browsers to store and reuse them. Cached stylesheets skip the network on repeat visits, reducing load time for returning users while still allowing updates through versioned filenames.
JavaScript Minification Test
98% of top 100 sites passed
All JavaScript files used by this webpage are minified.
Detects whether external JavaScript files are minified by stripping whitespace, comments, and shortening identifiers. Minified scripts are substantially smaller and faster to download and parse, which lowers page load time and improves Core Web Vitals scores.
CSS Minification Test
100% of top 100 sites passed
All CSS resources used by this webpage are minified.
Detects whether external CSS files are minified by removing whitespace, comments, and unused characters. Minification reduces stylesheet size with no functional change, leading to faster downloads and quicker first render.
Render Blocking Resources Test
15% of top 100 sites passed
This webpage is using render blocking resources! Eliminating render-blocking resources can help this webpage to load significantly faster and will improve the website experience for your visitors.

Render Blocking Resources Test

How to pass this test?

This test fails when JavaScript or CSS resources block the browser from rendering visible content. Each render-blocking file delays the first paint, and on slower networks the cumulative impact can be severe. Fixing this issue means inlining the truly critical CSS, deferring or asynchronously loading non-essential scripts, and removing unused code.

Example

<head>
  <!-- Inline only above-the-fold critical CSS -->
  <style>/* critical styles here */</style>

  <!-- Load full stylesheet asynchronously -->
  <link rel="preload" href="/styles/main.css" as="style"
        onload="this.onload=null;this.rel='stylesheet'">

  <!-- Defer non-critical scripts -->
  <script src="/scripts/app.js" defer></script>
</head>

Where to make the change

  • Application code or templates: identify the CSS and JavaScript needed for the initial render and load only those synchronously. Defer the rest.
  • Build pipeline: use a critical CSS extractor (such as critical or penthouse) to generate the above-the-fold styles automatically.
  • WordPress: performance plugins offer "delay JS execution" and "load CSS asynchronously" options that handle most of this without code changes.
  • Headless or framework sites: use the framework's preload and code-splitting hints to control what blocks rendering.

Common causes and how to resolve them

  • Single large stylesheet blocking render: inline critical CSS for the first viewport, load the full stylesheet asynchronously.
  • Synchronous third-party scripts in the head: add defer or async, or move them to the end of the body.
  • Web fonts blocking text rendering: add font-display: swap in @font-face rules so the fallback font shows immediately.
  • Render-blocking @import in CSS: replace with separate <link rel="stylesheet"> tags so the browser can fetch them in parallel.

Best practices

  • Use defer for scripts that need the DOM: they execute after parsing but before DOMContentLoaded.
  • Use async for fully independent scripts: they execute as soon as they download, in any order.
  • Preload the critical request chain: tell the browser early about fonts and key assets with <link rel="preload">.
  • Audit with Lighthouse: the Render-blocking resources audit lists every offending file with the estimated time saved by deferring it.
Identifies JavaScript and CSS resources that the browser must download and process before it can render visible content. Each render-blocking file delays the first paint, and on slower networks the cumulative impact can be severe. Inlining critical styles, deferring non-essential scripts, and removing unused code all help unblock the rendering path.
URL Redirects Test
97% of top 100 sites passed
This URL performed 1 redirects! While redirects are typically not advisable (as they can affect search engine indexing issues and adversely affect site loading time), one redirect may be acceptable, particularly if the URL is redirecting from a non-www version to its www version, or vice-versa.
Counts the number of HTTP redirects required for the URL to resolve to its final destination. Each hop adds latency and can dilute link equity, while long redirect chains sometimes confuse crawlers and indexing pipelines. Keeping redirects short and direct is a Google recommendation for both performance and SEO.
Time To First Byte Test
99% of top 100 sites passed
The Time To First Byte value of this webpage is 1.438 seconds. To provide a good user experience, Google recommends that sites should strive to have a TTFB of 0.8 seconds or less.
1.438 s
0.8 s
1.8 s

Time To First Byte Test

How to pass this test?

Time to First Byte (TTFB) measures the delay between the browser requesting the page and the first byte of the response arriving. TTFB reflects backend, network, and CDN performance and effectively sets the floor for every other loading metric, since rendering cannot begin until bytes start flowing. Fixing this issue usually means improving server response time, adding edge caching, or reducing redirect chains.

Where to make the change

  • Server and hosting: upgrade to a faster host plan, move to a region closer to your users, and enable HTTP/2 or HTTP/3.
  • CDN: putting the site behind a CDN dramatically reduces TTFB for users far from the origin server. Cache HTML responses at the edge whenever possible.
  • Application code: profile slow endpoints, cache expensive database queries and external API calls, and use streaming or partial responses.

Common causes and how to resolve them

  • Slow server processing: profile the slowest controllers or routes. Database queries, N+1 loops, and synchronous third-party API calls are typical culprits.
  • No edge caching: caching HTML at the CDN reduces TTFB to a single edge round trip. Use rules to bypass cache for logged-in users.
  • Long redirect chains: each hop adds latency before bytes flow. Collapse chains so the URL the user requests resolves to its final destination in one step.
  • Origin in a distant region: a US-only origin makes Asian users wait. Add edge regions or move the origin closer to the audience.
  • HTTP/1.1 or no keep-alive: upgrading to HTTP/2 or HTTP/3 reduces connection setup overhead.

Best practices

  • Target sub-800 millisecond TTFB at the 75th percentile: Google's recommended threshold for a "good" experience.
  • Cache aggressively: the cheapest server work is the work you never do. Static and semi-static pages should be served from cache.
  • Use HTTP/3 where supported: it eliminates head-of-line blocking and reduces handshake latency, especially on mobile networks.
  • Stream the response when possible: sending the head before the rest of the body lets the browser start fetching subresources earlier.
Measures Time to First Byte, the delay between the browser requesting the page and the first byte of the response arriving. TTFB reflects backend, network, and CDN performance and effectively sets the floor for every other loading metric, since rendering cannot begin until bytes start flowing. Sustained high TTFB usually points to slow server processing, missing edge caching, or inefficient redirects.
First Contentful Paint Test
90% of top 100 sites passed
The First Contentful Paint value of this webpage is 3.552 seconds. To provide a good user experience, Google recommends that sites should strive to have a First Contentful Paint value of 1.8 seconds or less.
3.552 s
1.8 s
3 s

First Contentful Paint Test

How to pass this test?

First Contentful Paint (FCP) measures the time from when the page starts loading to when any part of its content is rendered on the screen. FCP is the user's first visual confirmation that the page is loading, and faster values are strongly correlated with lower bounce rates and better Core Web Vitals scores. Fixing this issue means reducing time to first byte, eliminating render-blocking resources, and serving above-the-fold content without delay.

Where to make the change

  • Server and CDN: reduce TTFB so the browser receives bytes sooner. Edge caching for HTML produces dramatic FCP wins.
  • Application code or templates: inline the critical CSS for above-the-fold content and defer everything not needed for the first paint.
  • Build pipeline: ensure JavaScript bundles are split so the initial load only includes what is needed for first render.

Common causes and how to resolve them

  • Slow TTFB: address the underlying server, redirect, or hosting issue (see Time to First Byte fix).
  • Render-blocking CSS: inline the critical CSS for the first viewport, load the full stylesheet asynchronously.
  • Render-blocking JavaScript in the head: add defer or move scripts to the end of the body.
  • Web fonts delaying text rendering: add font-display: swap so a fallback font is shown immediately while the custom font loads.
  • Heavy hero image without prioritization: add fetchpriority="high" to the hero image and <link rel="preload"> for it in the head.

Best practices

  • Target sub-1.8 second FCP at the 75th percentile: Google's recommended threshold for a "good" experience.
  • Inline critical CSS: the styles needed for the first viewport should not require an extra network round trip.
  • Preload key resources: hero image, key fonts, and critical scripts benefit from explicit preload hints.
  • Defer non-critical work: analytics, chat widgets, and below-the-fold content can wait until after first paint.
Measures First Contentful Paint, the moment when the browser renders the first piece of visible content from the DOM, such as text, an image, or an SVG. FCP is the first signal to the user that the page is actually loading, and faster values are strongly correlated with lower bounce rates and better Core Web Vitals scores.
Largest Contentful Paint Test
77% of top 100 sites passed
The Largest Contentful Paint duration of this webpage is 3.64 seconds. To provide a good user experience, Google recommends that sites should strive to have Largest Contentful Paint of 2.5 seconds or less.
3.64 s
2.5 s
4 s
Largest Contentful Paint element within the viewport:
<img fetchpriority="high" decoding="async" width="1020" height="319" src="https://mygiftcardsite.caiqueparrots.com/wp-conten..." class="attachment-large size-large" alt="AD88-banner" srcset="https://mygiftcardsite.caiqueparrots.com/wp-conten..." sizes="(max-width: 1020px) 100vw, 1020px">

Largest Contentful Paint Test

How to pass this test?

Largest Contentful Paint (LCP) measures when the largest visible element in the viewport, such as a hero image or main heading, finishes rendering. LCP is one of Google's Core Web Vitals and a direct ranking factor, used as a proxy for when the user perceives the page as effectively loaded. Fixing this issue means identifying the LCP element and ensuring it loads as early as possible.

Where to make the change

  • Identify the LCP element: open Chrome DevTools, run a Performance trace, and find the LCP marker. The element it points at is the one to optimize.
  • Application code or templates: preload the LCP image, give it fetchpriority="high", and ensure it is in the initial HTML rather than injected by JavaScript.
  • Server and CDN: reduce TTFB and ensure the LCP image is served from a fast, geographically close origin.

Common causes and how to resolve them

  • Hero image loaded lazily: remove loading="lazy" from the LCP image; it should load eagerly.
  • LCP image not preloaded: add <link rel="preload" as="image" href="/hero.jpg" fetchpriority="high"> in the head so the browser fetches it before parsing the rest of the document.
  • LCP image too large or in legacy format: resize to displayed dimensions and serve as WebP or AVIF.
  • Slow TTFB or render-blocking resources: address the underlying TTFB and render-blocking issues; LCP cannot be fast if the page itself is slow to start.
  • Client-side rendered hero content: server-render or pre-render the LCP element so it appears in the initial HTML.
  • Web fonts delaying LCP text: use font-display: swap so the LCP heading renders immediately in a fallback font.

Best practices

  • Target sub-2.5 second LCP at the 75th percentile: the official Core Web Vitals threshold for a "good" experience.
  • Preload the LCP image: the single highest-impact LCP optimization on most sites.
  • Use fetchpriority="high": tells the browser to prioritize the resource ahead of others.
  • Ship modern image formats: AVIF and WebP cut hero image bytes substantially, which directly lowers LCP.
Measures Largest Contentful Paint, the time at which the largest visible element in the viewport, such as a hero image or main heading, finishes rendering. LCP is one of Google's Core Web Vitals and a direct ranking factor, used as a proxy for when the user perceives the page as effectively loaded.
Cumulative Layout Shift Test
91% of top 100 sites passed
The CLS score of this webpage is 0.0078. To provide a good user experience, Google recommends that sites should strive to have a CLS score of 0.1 or less.
0.0078
0.1
0.25
DOM element which contributes the most to CLS score:
Score: 0.0078
Measures Cumulative Layout Shift, the total amount that visible elements move around unexpectedly while the page loads. Layout shifts cause users to misclick and feel the page is unstable, and CLS is one of Google's Core Web Vitals and a direct ranking factor. Common causes include images without explicit dimensions, late-loading fonts, and aggressively injected overlays such as cookie consent banners.

Server and security

Score:89
Failed:1
Warnings:0
Passed:6
URL Canonicalization Test
93% of top 100 sites passed
Detects whether different URL variants of the site, such as the apex domain and the www subdomain or HTTP and HTTPS, all resolve consistently to a single canonical version. When the same content is reachable at multiple URLs without proper redirects, search engines may split ranking signals across the variants and become unsure which one to index.
SSL Checker and HTTPS Test
100% of top 100 sites passed
This website is successfully using HTTPS, a secure communication protocol over the Internet.
The certificate is not used before the activation date.
The certificate has not expired.
The hostname "mygiftcardsite.caiqueparrots.com" is correctly listed in the certificate.
The certificate should be trusted by all major web browsers.
The certificate was not revoked.
The certificate was signed with a secure hash.
Certificate Chain:
Server certificate
Common Name
caiqueparrots.com
Subject Alternative Names
*.caiqueparrots.com, caiqueparrots.com
Not Valid Before
Wed, November 11, 2026 at 5:12:24 AM UTC
Not Valid After
Tue, February 9, 2027 at 5:12:23 AM UTC
Signature Algorithm
ecdsaWithSha384
Issuer
YE2
Intermediate certificate
Common Name
YE2
Organization
Let's Encrypt
Location
US
Not Valid Before
Wed, September 3, 2025 at 12:00:00 AM UTC
Not Valid After
Sat, September 2, 2028 at 11:59:59 PM UTC
Signature Algorithm
ecdsaWithSha384
Issuer
Root YE
Intermediate certificate
Common Name
Root YE
Organization
ISRG
Location
US
Not Valid Before
Wed, May 13, 2026 at 12:00:00 AM UTC
Not Valid After
Thu, September 2, 2032 at 11:59:59 PM UTC
Signature Algorithm
ecdsaWithSha384
Issuer
ISRG Root X2
Root certificate
Common Name
ISRG Root X2
Organization
Internet Security Research Group
Location
US
Not Valid Before
Fri, September 4, 2020 at 12:00:00 AM UTC
Not Valid After
Mon, September 17, 2040 at 4:00:00 PM UTC
Signature Algorithm
ecdsaWithSha384
Issuer
ISRG Root X2
Verifies whether the site is served over HTTPS with a valid TLS certificate. HTTPS encrypts the connection between visitor and server, protecting credentials and other sensitive data in transit, and Google has used it as a positive ranking signal since 2014. Modern browsers also flag non-HTTPS pages as Not Secure, which damages user trust.
Mixed Content Test (HTTP over HTTPS)
100% of top 100 sites passed
This webpage does not use mixed content - both the initial HTML and all other resources are loaded over HTTPS.
Detects whether a page served over HTTPS is loading any sub-resources such as images, scripts, or stylesheets over insecure HTTP. Mixed content weakens the security guarantees of HTTPS, and modern browsers either block the resources outright or warn the user, often breaking the page in the process.
HTTP2 Test
99% of top 100 sites passed
This webpage is using the HTTP/2 protocol.
Verifies whether the page and its resources are delivered over HTTP/2 or newer, rather than the legacy HTTP/1.1 protocol. HTTP/2 introduces multiplexing, header compression, and prioritization, which together reduce latency and allow the browser to load many resources from the same origin far more efficiently.
HSTS Test
84% of top 100 sites passed
This webpage is using the Strict-Transport-Security header.
strict-transport-security:max-age=31536000
Checks whether the server sends a Strict-Transport-Security header instructing browsers to only access the site over HTTPS. HSTS protects users from protocol downgrade attacks and accidental exposure to insecure connections, and is a baseline requirement for any site handling sensitive data.
Plaintext Emails Test
97% of top 100 sites passed
This webpage does not include email addresses in plaintext.
Scans the page for email addresses written in plain text. Spambots harvest such addresses to add them to bulk mailing lists, so obfuscating contact emails or replacing them with contact forms helps reduce inbox spam without hiding the address from legitimate visitors.

Mobile usability

Score:100
Failed:0
Warnings:0
Passed:3
Meta Viewport Test
92% of top 100 sites passed
This webpage is using a viewport meta tag.
<meta name="viewport" content="width=device-width, initial-scale=1" />
Checks whether the page declares a viewport meta tag that controls how the layout scales on mobile devices. Without it, mobile browsers render the page at a default desktop width and shrink it to fit, producing unreadable text and unusable touch targets. A correct viewport declaration is the foundation of responsive design.
Media Query Responsive Test
98% of top 100 sites passed
This webpage is using CSS media queries, which is the base for responsive design functionalities.
Detects whether the page's stylesheets use CSS media queries to adapt the layout to different screen sizes. Media queries are the primary mechanism for responsive design, allowing typography, spacing, and component arrangement to adjust gracefully from phones to large desktops. Because Google now indexes the web mobile-first, the responsive mobile layout is effectively the version search engines crawl, evaluate, and rank.
Mobile Snapshot Test
Mobile view
A rendered screenshot of how the page appears on a mobile device. Useful for visually confirming that responsive layouts work as intended and for spotting issues such as overflowing content, illegible text, or broken images that automated checks alone may miss.

Advanced SEO

Score:45
Failed:4
Warnings:1
Passed:4
Structured Data Test
66% of top 100 sites passed
This webpage is using structured data. It describes the page's content in a machine-readable format that can help search engines and AI assistants understand it. With the right properties, the page can be eligible for rich results in search, like star ratings or product details.
Inspects the page for structured data markup such as JSON-LD or Microdata that follows schema.org vocabularies. Structured data helps search engines understand entities and relationships on the page, often unlocking rich result features in SERPs such as star ratings, FAQs, recipes, and product cards. It is also a primary signal AI answer engines use to extract precise facts when generating responses.
Custom 404 Error Page Test
80% of top 100 sites passed
This website is not using a custom 404 error page! Default 404 error pages result in a poor experience - it can mislead users into thinking an entire site is down or broken, greatly increases the chance they leave the website entirely, and looks unprofessional. We recommend to have a custom 404 error page in order to improve the website's user experience by letting users know that only a specific page is missing/broken (and not the entire site), providing them helpful links, the opportunity to report bugs, and potentially track the source of broken links.

Custom 404 Error Page Test

How to pass this test?

This test fails when the site does not serve a branded, helpful page for missing URLs. A custom 404 keeps users on the site by offering navigation, search, and suggested links rather than dropping them at the browser's generic error screen. Fixing this issue means designing a 404 template, ensuring it returns the correct HTTP 404 status, and pointing your server at it.

Where to make the change

  • Server configuration: point your web server at a custom 404 page. In Nginx, use error_page 404 /404.html;. In Apache, use ErrorDocument 404 /404.html.
  • WordPress: create a 404.php template in your theme. WordPress invokes it automatically for missing URLs.
  • Shopify: edit the 404.liquid template in the theme code editor.
  • Wix or Squarespace: use the platform's built-in 404 page editor in site settings.
  • Headless or framework sites: Next.js uses not-found.js, Astro uses 404.astro, and similar frameworks all have a convention for the missing-route page.

Common causes and how to resolve them

  • No custom 404 at all: create one. The minimum is the site header, navigation, a clear "page not found" message, and links to popular sections.
  • 404 page returns HTTP 200: a "soft 404" confuses search engines. Verify the response status with DevTools or curl, and configure the server to return 404 for missing routes.
  • 404 page redirects to homepage: redirecting users to the homepage hides broken URLs from analytics and search engines. Show a real 404 instead.
  • Generic browser error visible: the server is not invoking the custom template. Check the configuration directive.

Best practices

  • Keep the site chrome: show the header, footer, and navigation so users do not feel lost.
  • Offer next steps: a search box, popular links, or category navigation help users get back on track.
  • Track 404s: log missing-URL hits in analytics so you can spot broken inbound links worth fixing or redirecting.
  • Be clear about the error: "Sorry, that page does not exist" is better than vague messaging that confuses users.
Detects whether the site serves a branded, helpful page when a requested URL is not found, instead of the browser's generic error screen. A custom 404 keeps users on the site by offering navigation, search, or suggested links, which reduces frustration and protects engagement metrics that influence both UX perception and indirect SEO outcomes.
Noindex Tag Test
99% of top 100 sites passed
This webpage does not use the noindex meta tag. This means that it can be indexed by search engines.
Detects whether the page is being excluded from search engine indexes via a noindex directive in the robots meta tag or X-Robots-Tag HTTP header. A noindex on the wrong page is one of the most common ways important content silently disappears from search results, so verifying its absence on pages meant to rank is critical.
Canonical Tag Test
93% of top 100 sites passed
This webpage is using the canonical link tag. This tag specifies that the URL: https://mygiftcardsite.caiqueparrots.com/vn/ should be the preferred version of this page. The canonical tag can be useful when there are similar versions of the same content on several URLs (e.g., such as e-commerce sites where URL modifiers like sort parameters are appended to a product page's URL). Please ensure that this specification is correct, as canonical tags are often hard-coded and may not always reflect the latest changes in a site's URL structure.
<link href="https://mygiftcardsite.caiqueparrots.com/vn/" rel="canonical"/>

Canonical Tag Test

How to pass this test?

The canonical link tag declares the preferred URL for a page when the same or similar content is reachable at multiple URLs. Fixing this issue means adding a <link rel="canonical"> tag to every page that points at the URL you want indexed, which consolidates ranking signals onto the canonical version and helps AI crawlers identify the source of truth when citing the page. See the Google canonicalization guide for the full specification.

Example

<head>
  <link rel="canonical" href="https://example.com/shoes/marathon">
</head>

Where to make the change

  • Raw HTML: add a single <link rel="canonical"> inside the <head>. The href must be an absolute URL.
  • WordPress: a dedicated SEO plugin emits canonical tags automatically. Override per-post when the auto-derived URL is wrong.
  • Shopify: the default Liquid layout emits canonical tags from {{ canonical_url }}. Confirm your custom theme has not removed them.
  • Wix or Squarespace: both platforms emit canonical tags automatically; per-page override fields are available in SEO settings.
  • Headless or framework sites: emit the canonical tag from the framework's metadata API alongside title and description.

Common causes and how to resolve them

  • No canonical tag at all: add one pointing at the page's preferred URL.
  • Canonical points to the wrong page: a templating bug can point every page's canonical at the homepage. Verify the value matches the current URL on a sample of pages.
  • Canonical uses a relative URL: always use the full https:// URL. Relative paths can be misinterpreted.
  • Multiple canonical tags on the same page: only one should exist. A theme and an SEO plugin sometimes both emit one. Pick a single source.
  • Canonical conflicts with a noindex tag: if a page is noindexed, the canonical pointing at it has no effect. Resolve which signal you actually want.

Best practices

  • Self-canonicalize when in doubt: if a page has no duplicates, it should canonicalize to itself.
  • Pair with consistent internal linking: link to the canonical URL from internal navigation, not to query-parameter variants.
  • Use canonicals for pagination and filters: filtered or sorted product list URLs typically canonicalize to the unfiltered base view.
  • Verify with URL Inspection: Google Search Console reports the canonical Google has chosen, which may differ from the one you declared.
Detects whether the page declares a canonical link tag indicating its preferred URL. Canonical tags consolidate ranking signals across duplicate or near-duplicate URLs onto a single authoritative version, which prevents search engines from splitting authority across variants caused by query parameters, session IDs, or alternate paths. They also help AI crawlers identify the source of truth when citing the page.
Nofollow Tag Test
This webpage is using the nofollow meta tag! We recommend to use this tag carefully since search engines will not crawl all links from this webpage.

Nofollow Tag Test

How to pass this test?

This test reports on whether the page applies a nofollow directive that tells search engines not to follow outbound links. The nofollow attribute (and the related sponsored and ugc values) controls how link equity flows from your page. Fixing this issue means using the right rel value on each external link based on its purpose so signals are passed only where you intend.

Where to make the change

  • Raw HTML: add rel="nofollow", rel="sponsored", or rel="ugc" to specific outbound links rather than blanket-applying them site-wide.
  • WordPress: the block editor offers a "mark as nofollow" option per link, and SEO plugins can auto-tag external links by domain.
  • Shopify, Wix, Squarespace: editor-generated links allow rel attribute toggles; manual HTML embeds need them set explicitly.
  • Headless or framework sites: wrap external links in a component that decides the rel based on the link's classification.

Common causes and how to resolve them

  • Site-wide nofollow on every external link: overly aggressive. Reserve nofollow for sponsored, untrusted, or user-generated content.
  • Sponsored content not labeled: use rel="sponsored" on paid placements and affiliate links to comply with Google's link spam policy.
  • User-generated content unmarked: comments, forum posts, and review user submissions should use rel="ugc".
  • Trusted editorial links nofollowed: these should pass equity. Remove the nofollow.

Best practices

  • Use the most specific value: sponsored for paid links, ugc for user content, nofollow for everything else you want to disclaim. They can be combined: rel="sponsored noopener".
  • Do not nofollow internal links: "PageRank sculpting" with internal nofollow no longer works and just wastes crawl signal.
  • Audit periodically: as content ages, sponsored relationships change. Review affiliate and partner links once a year.
Detects whether the page applies a nofollow directive, either through a robots meta tag, an X-Robots-Tag header, or per-link rel attributes, that tells search engines not to follow outbound links. Google recommends nofollow for sponsored links and for user-generated content where the linked sites are not vetted, so its presence or absence has real consequences for how link equity flows.
Disallow Directive Test
Your robots.txt file includes a disallow command which instructs search engines to avoid certain parts of your website! You are advised to confirm if access to these resources or pages are intended to be blocked (e.g., if they contain internal-only content or sensitive information).
Surfaces the disallow rules declared in the site's robots.txt file. Disallow directives tell search engine crawlers not to access specific files, paths, or directories, which is useful for keeping admin sections and duplicate content out of indexes but dangerous when applied too broadly, since over-blocking can hide important pages from search.
Meta Refresh Test
98% of top 100 sites passed
This webpage is not using a meta refresh tag.
Detects whether the page uses a meta refresh tag to automatically reload or redirect after a delay. Meta refresh is largely obsolete, hurts accessibility by jumping focus and disorienting screen reader users, and is a weaker signal to search engines than a proper server-side 301 redirect. Its presence usually indicates outdated implementation worth updating.
SPF Records Test
94% of top 100 sites passed
This DNS server is not using an SPF record! SPF (Sender Policy Framework) allows administrators to specify which hosts are allowed to send mail from a given domain by creating a specific SPF record or TXT record in the Domain Name System (DNS). You can find more information about SPF records here.

SPF Records Test

How to pass this test?

The Sender Policy Framework (SPF) DNS record lists the mail servers authorized to send email on behalf of your domain. Receiving servers use it to verify that messages claiming to come from your domain are legitimate, which significantly reduces the chance of email being marked as spam. Fixing this issue means publishing an SPF record in your DNS that includes every legitimate sender and ends with a strict policy.

Example

example.com.  TXT  "v=spf1 include:_spf.google.com include:mailgun.org ~all"

Where to make the change

  • DNS provider: add a TXT record at the domain root with the SPF policy. Cloudflare, Route 53, Namecheap, GoDaddy, and similar all expose a TXT record editor.
  • Email providers: Google Workspace, Microsoft 365, and most transactional email services publish their required SPF include directives in their setup documentation.

Common causes and how to resolve them

  • No SPF record at all: add one. Even a minimal record (v=spf1 include:_spf.google.com ~all) is better than nothing.
  • Multiple SPF records: SPF only allows one TXT record per domain. Merge multiple records into a single one with all required include: directives.
  • Policy too permissive: ending with +all authorizes anyone to send as your domain. Use ~all (soft fail) or -all (hard fail) instead.
  • Missing legitimate senders: add an include: for every transactional email service (SendGrid, Mailgun, Postmark) and every marketing platform you use.
  • Too many DNS lookups: SPF caps include lookups at ten. Flatten or consolidate include: chains if you exceed it.

Best practices

  • Pair SPF with DKIM and DMARC: SPF alone is not enough. DKIM signs messages cryptographically; DMARC tells receivers what to do when SPF or DKIM fails.
  • Start with ~all, move to -all: soft fail lets you observe before strict enforcement. Move to hard fail once you are confident no legitimate sender is missing.
  • Test deliverability: tools such as MXToolbox SPF check or Google Postmaster Tools surface SPF problems before users complain.
  • Audit annually: as you add or remove email vendors, the SPF record needs to keep up.
Checks the domain's DNS for a Sender Policy Framework record. SPF lets receiving mail servers verify that messages claiming to come from the domain were actually sent by an authorized mail server, which significantly reduces the chance of legitimate email being marked as spam and protects the domain's sender reputation.
Ads.txt Validation Test
67% of top 100 sites passed
This website doesn't use an ads.txt file! Ads.txt is a text file that contains a list of Authorized Digital Sellers. The purpose of ads.txt files is to give advertisers and advertising networks the ability to verify who is allowed to sell advertising on your website.
Validates the format of the site's ads.txt file, which publishers use to declare which advertising vendors are authorized to sell their inventory programmatically. A correctly formatted ads.txt protects against domain spoofing in the ad supply chain and is required for inclusion in many premium advertising marketplaces.

Dominate search today on Google and AI Engines.

Join 85,000+ SaaS Marketers, Growth Agencies, Content-Led Companies and E-commerce Brands.

See Pricing
Dashboard preview showing SEO site checkup metrics, page group insights, and issue prioritization