Website review, no card needed
ajeeb.net website review
Visit site (opens in a new tab)Reviewed 12 November 202635 issues · 92 checks
This review found 35 issues worth fixing on ajeeb.net, 11 of them high impact, across 92 checks. The most urgent: use efficient cache lifetimes. 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
82B- #30,995 of 109,350 reviewed websitesbeats 66%
- #20,633 of 61,859 online storesbeats 60%
- #19,953 of 56,401 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.2 s |
| Nov 7, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 137 ms |
| May 30, 2026 | 143 ms |
| Jun 6, 2026 | 145 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 148 ms |
| Jun 27, 2026 | 147 ms |
| Jul 4, 2026 | 145 ms |
| Jul 11, 2026 | 145 ms |
| Jul 18, 2026 | 140 ms |
| Jul 25, 2026 | 144 ms |
| Aug 1, 2026 | 146 ms |
| Aug 8, 2026 | 147 ms |
| Aug 15, 2026 | 154 ms |
| Aug 22, 2026 | 155 ms |
| Aug 29, 2026 | 155 ms |
| Sep 5, 2026 | 162 ms |
| Sep 12, 2026 | 174 ms |
| Sep 19, 2026 | 171 ms |
| Sep 26, 2026 | 176 ms |
| Oct 3, 2026 | 178 ms |
| Oct 10, 2026 | 168 ms |
| Oct 17, 2026 | 162 ms |
| Oct 24, 2026 | 160 ms |
| Oct 31, 2026 | 162 ms |
| Nov 7, 2026 | 169 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
Use efficient cache lifetimes
1.5 s · 468 KiB33 files are served with short cache lifetimes, so returning visitors download them again (468 KiB).
Reduce unused JavaScript
1.2 s · 204 KiBAbout 204 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Render-blocking requests
1.1 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
Font display
600 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 600 ms).
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,194 HTML elements
The page has 2,194 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Clarity, Shopify and Snapchat and others), adding 796 KiB and 346 ms of main-thread time.
Reduce unused CSS
150 ms · 55 KiBAbout 55 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
203 KiB15 images could be 203 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 67 ms. During a long task the page ignores taps.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.6 s
14.6 sYour largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 14.7 s
14.7 sThe page becomes fully interactive after 14.7 s. Good is under 3.8 s.
64 images without width and height
64 images have no width and height attributes, so the layout jumps as each one loads.
Speed Index: 3.9 s
3.9 sVisually, the page fills in at 3.9 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 137 ms to 169 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 150 ms
150 msReal visitors wait 150 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 430 ms
430 msReal visitors wait 430 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.017
0.017The layout barely moves while loading (CLS 0.017, good is under 0.1).
Total Blocking Time: 55 ms
55 msScripts block the page for only 55 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.7 MB in 246 requests
2.7 MBYour homepage downloads 2.7 MB in 246 requests on a phone: other files 916 KiB (135), scripts 886 KiB (53) and images 596 KiB (44). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (58 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 0.8 g of CO₂ per visit
0.78 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.78 g of CO₂e: 93.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
33 buttons without a name
33 buttons have no accessible name, so screen readers announce just “button”.
Hidden but focusable
10 elements hidden from screen readers can still receive keyboard focus.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
67 images without alt text
67 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
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.
33 form fields without a label
33 form fields have no label, so screen readers announce an empty box and autofill guesses.
20 links without text
20 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (24 characters)
Your title is only 24 characters: “عجيب - متعة . تنوع . ثقة”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (306 characters)
Your meta description is 306 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization, WebPage and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
217 internal links, 16 external
The homepage links to 217 pages on ajeeb.net and 16 external pages.
5 checks passed
One H1 headline
Your main headline reads: “<img src="//ajeeb.net/cdn/shop/files/ajeeb_logo-38_200x.png?v=1721807215" srcset="//ajeeb.net/cdn/shop/files/ajeeb_logo…”.
Canonical URL set
The canonical URL is https://ajeeb.net/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://ajeeb.net/sitemap.xml.
AI search readiness
4 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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (355 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://ajeeb.net/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://ajeeb.net/pages/%D8%AE%D8%AF%D9%85%D8%A9-%D8%A7%D9%84%D8%B2%D8%A8%D8%A7%D8%A6%D9%86 has no meta description, so Google writes the search snippet from whatever text it finds.
14 links to non-canonical URLs
Your homepage links to 14 pages by a URL that isn't their canonical one, for example https://ajeeb.net/pages/%D8%AE%D8%AF%D9%85%D8%A9-%D8%A7%D9%84%D8%B2%D8%A8%D8%A7%D8%A6%D9%86, whose canonical is https://ajeeb.net/pages/%d8%ae%d8%af%d9%85%d8%a9-%d8%a7%d9%84%d8%b2%d8%a8%d8%a7%d8%a6%d9%86. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page with very little text
https://ajeeb.net/pages/%D8%AE%D8%AF%D9%85%D8%A9-%D8%A7%D9%84%D8%B2%D8%A8%D8%A7%D8%A6%D9%86 has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 95 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
42 distorted images
42 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “[AtlasPixel] Batch send failed: TypeError: Failed to fetch”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
56 of 64 tappable elements near the top are at least 24 px.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 271 words of copy
The homepage carries about 271 words of visible text.
4 checks passed
70 short forms
70 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel, Microsoft Clarity and Snap Pixel and 1 more (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
20 cookies set on arrival
20Opening the homepage sets 20 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.
31 other companies contacted
Loading the homepage contacts 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 ajeeb.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Social Login · Judge Me Reviews · Frequently Bought · Smart Menu · Bestpush · cloudfront.net · snapchat.com · hextom.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on ajeeb.net, including 11 speed issues, 4 SEO issues and 4 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.