Website review, no card needed
aparat.com website review
Visit site (opens in a new tab)Reviewed 12 October 202643 issues · 66 checks
This review found 43 issues worth fixing on aparat.com, 21 of them high impact, across 66 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
46FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 5.3 s |
| Apr 25, 2026 | 5.6 s |
| May 2, 2026 | 5.6 s |
| May 9, 2026 | 5.5 s |
| May 16, 2026 | 5.3 s |
| May 23, 2026 | 5.2 s |
| May 30, 2026 | 5.4 s |
| Jun 6, 2026 | 5.7 s |
| Jun 13, 2026 | 6.0 s |
| Jun 20, 2026 | 6.3 s |
| Jun 27, 2026 | 6.5 s |
| Jul 4, 2026 | 6.6 s |
| Jul 11, 2026 | 6.7 s |
| Jul 18, 2026 | 6.7 s |
| Jul 25, 2026 | 6.8 s |
| Aug 1, 2026 | 6.8 s |
| Aug 8, 2026 | 6.7 s |
| Aug 15, 2026 | 6.7 s |
| Aug 22, 2026 | 6.7 s |
| Aug 29, 2026 | 6.7 s |
| Sep 5, 2026 | 6.7 s |
| Sep 12, 2026 | 6.8 s |
| Sep 19, 2026 | 6.9 s |
| Sep 26, 2026 | 7.0 s |
| Oct 3, 2026 | 7.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 286 ms |
| Apr 25, 2026 | 296 ms |
| May 2, 2026 | 298 ms |
| May 9, 2026 | 301 ms |
| May 16, 2026 | 304 ms |
| May 23, 2026 | 306 ms |
| May 30, 2026 | 328 ms |
| Jun 6, 2026 | 357 ms |
| Jun 13, 2026 | 380 ms |
| Jun 20, 2026 | 402 ms |
| Jun 27, 2026 | 415 ms |
| Jul 4, 2026 | 416 ms |
| Jul 11, 2026 | 415 ms |
| Jul 18, 2026 | 419 ms |
| Jul 25, 2026 | 422 ms |
| Aug 1, 2026 | 425 ms |
| Aug 8, 2026 | 427 ms |
| Aug 15, 2026 | 428 ms |
| Aug 22, 2026 | 430 ms |
| Aug 29, 2026 | 431 ms |
| Sep 5, 2026 | 435 ms |
| Sep 12, 2026 | 438 ms |
| Sep 19, 2026 | 432 ms |
| Sep 26, 2026 | 429 ms |
| Oct 3, 2026 | 425 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Reduce unused JavaScript
2.6 s · 435 KiBAbout 435 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.6 s faster on a phone.
Mobile performance score: 23
23/100Your mobile performance score is 23 (desktop: 45). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.7 s
A phone's processor spends 4.7 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
600 ms · 101 KiB6 files are served with short cache lifetimes, so returning visitors download them again (101 KiB).
Render-blocking requests
450 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 262 ms. During a long task the page ignores taps.
Google Tag Manager adds 164 ms
164 msGoogle Tag Manager costs a phone 164 ms of main-thread work and 328 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Clarity and Yandex Metrica and others), adding 589 KiB and 269 ms of main-thread time.
Improve image delivery
50 KiB3 images could be 50 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 404 ms
404 msYour server sent the HTML in 404 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 5.6 s
5.6 sReal visitors wait 5.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.94
0.94For real visitors the layout shifts by 0.94 (75th percentile). Good is under 0.1.
Real-user FCP: 4.0 s
4.0 sReal visitors see the first content after 4.0 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 13.9 s
13.9 sYour largest element takes 13.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “اعتبار حساب کالابرگ ۱۱ میلیون نفر افزایش یافت”.
Cumulative Layout Shift: 0.949
0.949The layout shifts by 0.949 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 10.5 s
10.5 sVisually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 13.9 s
13.9 sThe page becomes fully interactive after 13.9 s. Good is under 3.8 s.
Total Blocking Time: 779 ms
779 msScripts block taps and scrolling for 779 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 272 ms
272 msReal visitors wait 272 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 47% slower for real visitors
+47%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 286 ms to 425 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 28% slower for real visitors
+28%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 5.3 s to 7.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user TTFB: 582 ms
582 msReal visitors wait 582 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
About 0.4 g of CO₂ per visit
0.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.43 g of CO₂e: 51.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.5 MB in 78 requests
1.5 MBYour homepage downloads 1.5 MB in 78 requests on a phone: scripts 1.2 MB (38), images 147 KiB (9) and fonts 69 KiB (1). That is a lean page.
Accessibility
Documents must have <title> element to aid in navigation (1 element)
Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
[role]s are not contained by their required parent element
[role]s are not contained by their required parent element (22 elements).
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Orphan list items
Some list items are not inside a list.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
1 checks passed
6 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 11 WCAG 2.2 A/AA and best-practice rules on the phone render: 6 passed and 5 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (27 characters)
Your title is only 27 characters: “آپارات - سرویس اشتراک ویدیو”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
2 checks passed
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.aparat.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.aparat.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
1 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “TypeError: Cannot read properties of undefined (reading 'register')”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 14 words
The homepage has only about 14 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
1 other company contacted
Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at aparat.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on aparat.com, including 19 speed issues, 7 SEO issues and 6 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.