Skip to main content
Archived

SEO Report for https://divar.ir

Your general SEO Checkup Score


SEO Score84/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 Visibility64/100
AI visibility score reflects brand reach in AI

Your site scored 84/100, comfortably above the 75 average for top sites. We found 8 issues to fix, and they're the gap between you and the very top. And an AI Visibility Score of 64/100 means ChatGPT, Gemini and Perplexity mention your brand some of the time, with clear room to push further.

8 Failed
1 Warnings
54 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
H1 and H2 tags ensure better search engine visibility and ranking by providing structure and hierarchy to the content, improving readability, and providing opportunities for keyword optimization.
Details
HIGH
To ensure that Search Engines can accurately identify the topic of this webpage, it is important to include the most common keywords in the title tag, meta description, and heading tags.
Details
HIGH
Add a sitemap file to help search engine crawlers index content more thoroughly and quickly.
Details
LOW
Consider reducing the HTML size to improve loading times and retain visitors.
Details
LOW
Resolving errors identified by the Chrome DevTools Console can improve user experience.
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

An online classifieds marketplace for buying and selling goods directly between users, with city-based browsing and a mobile/PWA app experience.

Industry Niche

Local online classifieds

Target Audience

People looking to buy, sell, or browse local secondhand and new items through a city-focused marketplace.

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 clear and highly focused on its core marketplace purpose, with simple guidance for browsing, posting, and using the web app. However, it is light on depth, with limited explanatory content beyond basic usage instructions and city links.

Content Strengths

  • Clear marketplace purpose
  • Simple user guidance
  • Local browsing structure

Content Weaknesses

  • Very limited depth
  • Minimal trust context
  • No content variety
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
63%
Topical Relevance98%
Subject Expertise72%
Credibility45%

This webpage appears moderately trustworthy because it includes official-looking verification badges and clear navigation to about, support, and news pages. Trust is limited by the absence of visible policy details, company background, leadership information, or cited methodology on this 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
68%

The page reads like a static homepage and help snippet rather than time-sensitive content, so freshness depends mostly on its ongoing service relevance. No explicit publish or update dates are visible, and the footer/legal timestamps are not shown, so there are few strong freshness signals either way.

Positive Signals

  • Current service instructions
  • Active city listings
  • PWA installation guidance

Staleness Signals

  • No visible publish dates
  • Static homepage-style copy
  • No recent update markers
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 communicates the core marketplace proposition well, but it leaves substantial room to deepen user guidance, trust, and conversion support. The biggest opportunities are around explaining how the platform works, reducing first-time user friction, and adding stronger proof of safety and reliability.

Quick Wins

  • •Add a short FAQ block covering posting, searching, and account basics.
  • •Place a visible trust-and-safety summary near the main call to action.
  • •Link the verification badges to a brief explanation of what each certification means.
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:69
Failed:4
Warnings:0
Passed:15
Meta Title Test
100% of top 100 sites passed
This webpage is using a title tag.
Text: دیوار: بزرگترین سایت نیازمندی های رایگان در ایران
Length: 49 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.
Text: دیوار مرجع اصلی نیازمندی های رایگان و خرید و فروش کالای نو و دست دوم. نیازمندی های املاک، خودرو، استخدام، لوازم خانه، خدمات و سایر بخش های مورد نظر شما
Length: 151 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://divar.ir/دیوار: بزرگترین سایت نیازمندی های رایگان در ایراندیوار مرجع اصلی نیازمندی های رایگان و خرید و فروش کالای نو و دست دوم. نیازمندی های املاک، خودرو، استخدام، لوازم خانه، خدمات و سایر بخش های مورد نظر شما
Mobile version
https://divar.ir/دیوار: بزرگترین سایت نیازمندی های رایگان در ایراندیوار مرجع اصلی نیازمندی های رایگان و خرید و فروش کالای نو و دست دوم. نیازمندی های املاک، خودرو، استخدام، لوازم خانه، خدمات و سایر بخش های مورد نظر شما
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.
Open Graph Meta Tags
og:site_nameسایت دیوار
og:typewebsite
og:urlhttps://divar.ir
og:titleدیوار: بزرگترین سایت نیازمندی های رایگان در ایران
og:descriptionدیوار مرجع اصلی نیازمندی های رایگان و خرید و فروش کالای نو و دست دوم. نیازمندی های املاک، خودرو، استخدام، لوازم خانه، خدمات و سایر بخش های مورد نظر شما
og:imagehttps://s100.divarcdn.com/web-assets/publics/android-chrome-512x512.png
og:localefa_IR
Twitter Card Meta Tags
twitter:cardsummary
twitter:site@divar_official
twitter:urlhttps://divar.ir
twitter:titleدیوار: بزرگترین سایت نیازمندی های رایگان در ایران
twitter:descriptionدیوار مرجع اصلی نیازمندی های رایگان و خرید و فروش کالای نو و دست دوم. نیازمندی های املاک، خودرو، استخدام، لوازم خانه، خدمات و سایر بخش های مورد نظر شما
twitter:imagehttps://s100.divarcdn.com/web-assets/publics/android-chrome-512x512.png
twitter:creatorسایت دیوار
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 is likely no optimal keyword density (search engine algorithms have evolved beyond keyword density metrics as a significant ranking factor). It can be useful, however, to note which keywords appear most often on your page and if they reflect the intended topic of your page. More importantly, the keywords on your page should appear within natural sounding and grammatically correct copy.
4اپلیکیشن
3دیوار
2دﯾﻮار
2ﭼﯿﺰی
2استفاده
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
The most common keywords of this webpage are not distributed across the important HTML tags! Primary keywords should appear in title tag, meta description and heading tags to help Search Engines to properly identify the topic of this webpage.
Keyword
Title tag
Meta description
Headings
اپلیکیشن
دیوار
دﯾﻮار
ﭼﯿﺰی
استفاده
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
home
screen
share
آگهی
آیکون
آﮔﻬﯿﺖ
اتاق
استفاده
اصفهان
انتخاب
اندروید
اهواز
اپلیکیشن
اﻧﺘﺨﺎب
بالا
بدون
برنامه
بزنید
تبریز
تنها
تهران
توانند
دانلود
درباره
دریافت
دسترسی
دکمه
دیوار
دﯾﻮار
دﺳﺘﻪ
دﻧﺒﺎل
دﻧﺒﺎﻟﺶ
رسانی
روزرسانی
سایر
سرویسی
شهرهای
شیراز
فراهم
قسمت
متوجه
مشهد
منوی
موبایل
نسخه
نوار
نیاز
نیازی
نیست
واﺳﻄﻪ
پایین
پربازدید
پشتیبانی
کاربران
کرمانشاه
کلیک
کنار
کنند
کنید
گزینه
ﭘﺎﯾﮕﺎه
ﭼﯿﺰی
ﺑﭽﺴﺒﻮن
ﺑﮕﯿﺮ
ﺑﮕﺮد
ﺑﻔﺮوﺷﯽ
ﺑﻨﺪی
ﺧﺮﯾﺪ
ﺧﻮای
ﺷﻬﺮت
ﻓﺮوش
ﻫﺴﺘﯽ
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 does not contain H1 headings! H1 headings help indicate the important topics of your page to search engines. While less important than good meta-titles and descriptions, H1 headings may still help define the topic of your page to search engines.
H2 tags
تهران
مشهد
کرج
شیراز
اصفهان
اهواز
تبریز
کرمانشاه
قم
رشت

Heading Tags Test

How to pass this test?

The H1 and H2 tags give search engines and assistive technology a clean outline of the page's topics. Fixing this issue means adding a single descriptive H1 and a logical hierarchy of H2 sub-sections so the page's structure is unambiguous to both users and machines. AI answer engines also use heading structure to segment content into discrete passages they can quote or summarize, so a clean hierarchy directly helps the page get picked up in generative results.

Example

<body>
  <h1>Lightweight Running Shoes for Marathons</h1>
  <h2>What to look for in a marathon shoe</h2>
  <h2>Top picks for 2026</h2>
  <h2>How we tested</h2>
</body>

Where to make the change

  • Raw HTML: add a single <h1> near the top of the page's main content, then use <h2> for major sections and <h3> for subsections under those.
  • WordPress: in the block editor, set the post title's heading level to H1 (themes usually do this automatically) and use the Heading block for in-body H2 and H3 sections.
  • Shopify: the product or page title field renders as an H1 in most themes. Use the rich-text editor to add H2 and H3 headings inside the body.
  • Wix or Squarespace: use the heading style picker in the block editor to assign H1, H2, and H3 levels rather than just changing font size.

Common causes and how to resolve them

  • No H1 on the page: add a single <h1> that names the page's primary topic. Many themes either skip the H1 or render the site logo as one.
  • Multiple H1s: while modern HTML allows multiple H1s, most SEO tools still flag them. Pick the most important one and demote the others to H2.
  • Headings used for visual styling only: bold or large text styled to look like a heading does not help search engines or screen readers. Use the actual heading tag and style it with CSS.
  • Hierarchy skips levels: jumping from H1 directly to H3 confuses assistive technology. Keep the order H1 then H2 then H3 without gaps.

Best practices

  • One H1 per page: reserve it for the page's main subject; treat it as the in-page equivalent of the title.
  • Make headings descriptive: each heading should make sense out of context. "How we tested" is better than "Methodology" alone if the page is a product review.
  • Include keywords naturally: H1 and H2 are mid-strength ranking signals. Use the focus keyword in the H1 and supporting terms in H2s when it reads naturally.
  • Outline the page from headings alone: if you can read just the H1 and H2s and understand what the page is about, the structure is doing its job.
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
This website lacks a sitemap file! Sitemaps can help robots index your content more thoroughly and quickly. Read more on Google's guidelines for implementing the sitemap protocol.

Sitemap Test

How to pass this test?

An XML sitemap gives search engines and AI crawlers an explicit, machine-readable list of the URLs you want indexed, along with metadata such as last-modified dates. Fixing this issue means generating a valid sitemap, publishing it at a stable URL, and pointing crawlers to it via robots.txt and Search Console. This is especially important for large sites, sites with weak internal linking, or sites where new content needs to be discovered quickly.

Example

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://example.com/</loc>
    <lastmod>2026-04-15</lastmod>
  </url>
  <url>
    <loc>https://example.com/blog/getting-started</loc>
    <lastmod>2026-03-22</lastmod>
  </url>
</urlset>

Where to make the change

  • Raw HTML or static site: generate the XML at build time and publish it at /sitemap.xml. Many static-site generators have a built-in sitemap option.
  • WordPress: a dedicated SEO plugin will generate and update the sitemap automatically, typically at /sitemap_index.xml.
  • Shopify: Shopify generates /sitemap.xml automatically and updates it as products and collections change.
  • Wix or Squarespace: both platforms generate the sitemap automatically and serve it at the standard root path.
  • Headless or framework sites: use the framework's built-in sitemap module (for example next-sitemap for Next.js or the @astrojs/sitemap integration) so the file is regenerated on every build.

Common causes and how to resolve them

  • No sitemap published: generate one and publish it at the site root. Reference it from robots.txt with a Sitemap: line.
  • Sitemap lists URLs that 404 or redirect: stale entries waste crawl budget and trigger Search Console warnings. Regenerate the sitemap from current published URLs only.
  • Mixed canonical and non-canonical URLs: the sitemap should list canonical URLs only. Listing both http and https, or trailing-slash variants, splits crawl signals.
  • Sitemap exceeds size limits: a single sitemap may contain at most 50,000 URLs and 50 MB uncompressed. Split larger sites into multiple sitemaps and reference them from a sitemap index file.

Best practices

  • Submit to Search Console: add the sitemap URL in Google Search Console (and Bing Webmaster Tools) so the platform tracks coverage and surfaces errors.
  • Keep lastmod accurate: Google uses lastmod as a hint when prioritizing crawls. Update it whenever the page content meaningfully changes; do not bump it on every build.
  • Exclude noindex and disallowed URLs: the sitemap should describe what you want indexed. Listing pages that are blocked from crawling sends mixed signals.
  • Use sitemap index files for multi-sitemap setups: a sitemap index aggregates child sitemaps (for example one per content type) and is the single URL you submit to search engines.
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 "img" tags from this webpage have the required "alt" attribute.
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
All images in this webpage are properly sized for different users' viewports.
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 image display dimensions match the natural aspect ratio.
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
This webpage does not use HTML deprecated tags.
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 is using Google Analytics.
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 appears to have a favicon.
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
There are no severe JavaScript errors on this webpage.
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
This webpage has some errors caught by the Chrome DevTools Console!

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 has a character encoding declaration.
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:87
Failed:3
Warnings:0
Passed:17
HTML Page Size Test
23% of top 100 sites passed
The size of this webpage's HTML is 42.78 Kb, and is greater than the average size of 33 Kb! This can lead to slower loading times, lost visitors, and decreased revenue. Good steps to reduce HTML size include: using HTML compression, CSS layouts, external style sheets, and moving javascript to external files.

HTML Page Size Test

How to pass this test?

This test fails when the raw HTML document weighs significantly more than necessary, even before counting images, CSS, or JavaScript. Bloated HTML increases time to first byte, slows parsing, and stalls rendering on mobile networks and lower-powered devices. Fixing this issue means trimming inline data, removing legacy markup, and keeping the document focused on what the user needs.

Where to make the change

  • Application code or templates: identify which sections produce the most bytes (often a large inline JSON blob, an inline base64 image, or a giant comment block) and refactor them to load externally or be removed.
  • WordPress: check for plugins or page builders that emit large inline configurations. Disable unused plugins and prefer themes that ship clean markup.
  • Shopify: theme code may inline large product or section JSON. Move heavy data to a fetch-on-demand endpoint when possible.
  • Headless or framework sites: review the rendered output for serialized state (for example __NEXT_DATA__ in Next.js) and trim what is sent on first paint by streaming or lazy-loading non-critical chunks.

Common causes and how to resolve them

  • Inline base64 images or fonts: move them to external files so the browser can cache them across requests.
  • Excessive inline CSS or JavaScript: link to external stylesheets and scripts so they cache. Inline only the truly critical CSS for above-the-fold content.
  • Large server-side JSON payloads: ship only the data needed for first render. Fetch the rest on demand.
  • Repeating boilerplate or commented-out code: strip comments and dead code in the production build.
  • HTML compression disabled: Gzip or Brotli compression often shrinks the response by half or more. Confirm the server sends the appropriate Content-Encoding header.

Best practices

  • Aim for under 100 KB of HTML: most pages can comfortably stay under this. Anything beyond a few hundred KB usually indicates structural bloat worth refactoring.
  • Enable compression: Gzip is the safe minimum, Brotli is even better for HTML and other text formats.
  • Defer non-critical content: rendering only what is needed for the initial viewport keeps both bytes and parse time down.
  • Audit periodically: add HTML size to your performance budget so regressions get caught in CI.
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 164 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 gzip compression on your code. The HTML code is compressed from 211.55 Kb to 42.78 Kb (80% 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 2.15 seconds and this is under 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
javascript
79.8 %
1.49 Mb
other
15.4 %
294.47 Kb
css
3.2 %
60.68 Kb
html
1.6 %
31.15 Kb
image
0.0 %
0 B
font
0.0 %
0 B
TOTAL
100%
1.87 Mb
Requests by content type
Content type
Percent
Requests
javascript
72.0 %
36
other
12.0 %
6
css
10.0 %
5
html
6.0 %
3
image
0.0 %
0
font
0.0 %
0
TOTAL
100%
50
Content size by domain
Domain
Percent
Size
s100.divarcdn.com
68.5 %
1.28 Mb
googletagmanager.com
26.3 %
502.33 Kb
map.divarcdn.com
3.6 %
68.44 Kb
divar.ir
1.6 %
30.87 Kb
sentry.divar.cloud
0.0 %
276 B
googleads.g.doubleclick.net
0.0 %
274 B
google.com
0.0 %
16 B
TOTAL
100%
1.87 Mb
Requests by domain
Domain
Percent
Requests
s100.divarcdn.com
84.0 %
42
googletagmanager.com
6.0 %
3
divar.ir
2.0 %
1
map.divarcdn.com
2.0 %
1
google.com
2.0 %
1
googleads.g.doubleclick.net
2.0 %
1
sentry.divar.cloud
2.0 %
1
TOTAL
100%
50
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 using images in a modern format.
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 image resources!
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 webpage is not using uncached images from same domain.
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 not using uncached JavaScript resources from same domain!
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 not using uncached CSS resources from same domain!
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 doesn't have any redirects (which could potentially cause site indexation issues and site loading delays).
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 0.191 seconds. To provide a good user experience, Google recommends that sites should strive to have a TTFB of 0.8 seconds or less.
0.191 s
0.8 s
1.8 s
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 0.836 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.
0.836 s
1.8 s
3 s
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 0.84 seconds. To provide a good user experience, Google recommends that sites should strive to have Largest Contentful Paint of 2.5 seconds or less.
0.84 s
2.5 s
4 s
Largest Contentful Paint element within the viewport:
Text: دﯾﻮار، ﭘﺎﯾﮕﺎه ﺧﺮﯾﺪ و ﻓﺮوش ﺑﯽ‌واﺳﻄﻪ‌! اﮔﻪ دﻧﺒﺎل ﭼﯿﺰی ﻫﺴﺘﯽ، ﺷﻬﺮت رو اﻧﺘﺨﺎب ﮐﻦ و ﺗﻮ...
Html: <p class="kt-body--sm home__description-f0214">
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.0036. To provide a good user experience, Google recommends that sites should strive to have a CLS score of 0.1 or less.
0.0036
0.1
0.25
DOM element which contributes the most to CLS score:
Html: <div class="home__links-a0494">
Score: 0.0036
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:100
Failed:0
Warnings:0
Passed:7
URL Canonicalization Test
93% of top 100 sites passed
https://divar.ir/ and https://www.divar.ir/ resolve to the same URL.
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 "divar.ir" 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
*.divar.ir
Subject Alternative Names
*.divar.ir, divar.ir
Not Valid Before
Sat, May 16, 2026 at 12:32:18 PM UTC
Not Valid After
Tue, December 1, 2026 at 12:32:17 PM UTC
Signature Algorithm
sha256WithRsaEncryption
Issuer
Certum DV TLS G2 R39 CA
Intermediate certificate
Common Name
Certum DV TLS G2 R39 CA
Organization
Asseco Data Systems S.A.
Location
PL
Not Valid Before
Tue, June 18, 2024 at 7:41:22 AM UTC
Not Valid After
Sun, June 5, 2039 at 7:41:22 AM UTC
Signature Algorithm
sha512WithRsaEncryption
Issuer
Certum Trusted Root CA
Root certificate
Common Name
Certum Trusted Root CA
Organization
Asseco Data Systems S.A.
Location
PL
Not Valid Before
Fri, March 16, 2018 at 12:10:13 PM UTC
Not Valid After
Mon, March 16, 2043 at 12:10:13 PM UTC
Signature Algorithm
sha512WithRsaEncryption
Issuer
Certum Trusted Root CA
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=992, 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:98
Failed:1
Warnings:1
Passed:7
Structured Data Test
66% of top 100 sites passed
This webpage is using structured data.
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 using a custom 404 error page. 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.
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://divar.ir/ is preferred to be used in search results. 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 data-react-helmet="true" href="https://divar.ir" rel="canonical"/>
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 using an SPF record.
v=spf1 include:one.zoho.eu ~all
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