Website review, no card needed
condor.dz website review
Visit site (opens in a new tab)Reviewed 4 November 202639 issues · 84 checks
This review found 39 issues worth fixing on condor.dz, 13 of them high impact, across 84 checks. The most urgent: render-blocking requests. 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
71C- #95,161 of 117,615 reviewed websitesbeats 16%
- #58,746 of 66,923 online storesbeats 10%
- #1,943 of 2,700 WooCommerce storesbeats 24%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 9.1 s |
| May 23, 2026 | 8.7 s |
| May 30, 2026 | 7.3 s |
| Jun 6, 2026 | 5.6 s |
| Jun 13, 2026 | 4.7 s |
| Jun 20, 2026 | 4.7 s |
| Jun 27, 2026 | 4.9 s |
| Jul 4, 2026 | 5.0 s |
| Jul 11, 2026 | 4.8 s |
| Jul 18, 2026 | 4.4 s |
| Jul 25, 2026 | 4.1 s |
| Aug 1, 2026 | 3.9 s |
| Aug 8, 2026 | 3.9 s |
| Aug 15, 2026 | 4.0 s |
| Aug 22, 2026 | 4.1 s |
| Aug 29, 2026 | 4.1 s |
| Sep 5, 2026 | 4.1 s |
| Sep 12, 2026 | 4.1 s |
| Sep 19, 2026 | 4.1 s |
| Sep 26, 2026 | 4.1 s |
| Oct 3, 2026 | 4.1 s |
| Oct 10, 2026 | 4.1 s |
| Oct 17, 2026 | 4.1 s |
| Oct 24, 2026 | 3.9 s |
| Oct 31, 2026 | 3.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 196 ms |
| May 23, 2026 | 190 ms |
| May 30, 2026 | 191 ms |
| Jun 6, 2026 | 199 ms |
| Jun 13, 2026 | 214 ms |
| Jun 20, 2026 | 234 ms |
| Jun 27, 2026 | 258 ms |
| Jul 4, 2026 | 263 ms |
| Jul 11, 2026 | 225 ms |
| Jul 18, 2026 | 162 ms |
| Jul 25, 2026 | 139 ms |
| Aug 1, 2026 | 131 ms |
| Aug 8, 2026 | 131 ms |
| Aug 15, 2026 | 138 ms |
| Aug 22, 2026 | 140 ms |
| Aug 29, 2026 | 139 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 138 ms |
| Sep 19, 2026 | 140 ms |
| Sep 26, 2026 | 141 ms |
| Oct 3, 2026 | 139 ms |
| Oct 10, 2026 | 138 ms |
| Oct 17, 2026 | 138 ms |
| Oct 24, 2026 | 141 ms |
| Oct 31, 2026 | 146 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
Render-blocking requests
4.8 s51 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.8 s.
Improve image delivery
3.6 s · 982 KiB19 images could be 982 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.6 s faster on a phone.
4,778 HTML elements
The page has 4,778 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
650 ms · 692 KiB139 files are served with short cache lifetimes, so returning visitors download them again (692 KiB).
Reduce unused CSS
900 ms · 194 KiBAbout 194 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 698 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Google Fonts and Cloudflare CDN and others), adding 351 KiB and 160 ms of main-thread time.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 187 ms. During a long task the page ignores taps.
Reduce unused JavaScript
110 KiBAbout 110 KiB of JavaScript is downloaded but never used on this page.
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
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 359 ms
359 msYour server sent the HTML in 359 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: 4.1 s
4.1 sReal visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest Contentful Paint: 11.1 s
11.1 sYour largest element takes 11.1 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.8 s
14.8 sThe page becomes fully interactive after 14.8 s. Good is under 3.8 s.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
Speed Index: 6.2 s
6.2 sVisually, the page fills in at 6.2 s (Speed Index). Good is under 3.4 s.
Real-user INP: 224 ms
224 msReal visitors wait 224 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.177
0.177The layout shifts by 0.177 while loading, so content jumps under the reader's thumb. Good is under 0.1.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
5 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 667 ms
667 msReal visitors wait 667 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 26% faster for real visitors
-26%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 196 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 57% faster for real visitors
-57%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 9.1 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 109 ms
109 msScripts block the page for only 109 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.1 MB in 159 requests
3.1 MBYour homepage downloads 3.1 MB in 159 requests on a phone: images 1.4 MB (33), fonts 771 KiB (8) and scripts 519 KiB (49). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
55-600x600.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
6 images in older formats
6 images (790 KiB) are 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.
1 image below the first screen load straight away
1 image further down the page (25 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.89 g of CO₂e: 106.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (26 elements)
All page content should be contained by landmarks: 26 elements on the page fail this check, rated moderate by axe-core.
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.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (5 elements)
Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 115 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 8 failed. 3 mores need a person to judge. 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.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
485 internal links, 26 external
The homepage links to 485 pages on condor.dz and 26 external pages.
5 checks passed
Title: 53 characters
Your title is a healthy 53 characters: “Condor - Leader de l'électroménager en Algérie Condor”.
Canonical URL set
The canonical URL is https://condor.dz/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, Person and WebPage.
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://condor.dz/sitemap_index.xml.
AI search readiness
Organization data is thin (1 of 6 facts)
Your Organization JSON-LD is missing url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://condor.dz/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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,616 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a meta description
https://condor.dz/qui-sommes-nous, https://condor.dz/notre-historique, https://condor.dz/nos-valeurs, https://condor.dz/tv-audio, https://condor.dz/product-category/tv-image-et-son/mini-led and https://condor.dz/product-category/tv-image-et-son/google-tv and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
12 pages without an H1
https://condor.dz/qui-sommes-nous, https://condor.dz/notre-historique, https://condor.dz/nos-valeurs, https://condor.dz/tv-audio, https://condor.dz/product-category/tv-image-et-son/google-tv and https://condor.dz/product-category/tv-image-et-son/gaming and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 76 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
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
10 small tap targets
10 of 31 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 411 words of copy
The homepage carries about 411 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “contact”.
3 calls to action
The homepage has 3 calls to action, for example “contact”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 8 phone links and 0 email links.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
5 other companies contacted
Loading the homepage contacts 5 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 condor.dz, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics
- Hosting
- Hostinger
Company
- Headquarters
- Bordj Bou Arréridj
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on condor.dz, including 17 speed issues, 3 SEO issues and 1 conversion gap. 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.