Website review, no card needed
fikr.com website review
Visit site (opens in a new tab)Reviewed 20 October 202641 issues · 83 checks
This review found 41 issues worth fixing on fikr.com, 20 of them high impact, across 83 checks. The most urgent: improve image delivery. 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
66D- #100,113 of 109,350 reviewed websitesbeats 7%
- #59,136 of 61,859 online storesbeats 4%
- #54,342 of 56,401 Shopify storesbeats 3%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.6 s |
| May 9, 2026 | 2.6 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 164 ms |
| May 9, 2026 | 173 ms |
| May 16, 2026 | 166 ms |
| May 23, 2026 | 185 ms |
| May 30, 2026 | 174 ms |
| Jun 6, 2026 | 173 ms |
| Jun 13, 2026 | 182 ms |
| Jun 20, 2026 | 194 ms |
| Jun 27, 2026 | 187 ms |
| Jul 4, 2026 | 175 ms |
| Jul 11, 2026 | 158 ms |
| Jul 18, 2026 | 136 ms |
| Jul 25, 2026 | 173 ms |
| Aug 1, 2026 | 184 ms |
| Aug 8, 2026 | 174 ms |
| Aug 15, 2026 | 166 ms |
| Aug 22, 2026 | 147 ms |
| Aug 29, 2026 | 139 ms |
| Sep 5, 2026 | 148 ms |
| Sep 12, 2026 | 150 ms |
| Sep 19, 2026 | 144 ms |
| Sep 26, 2026 | 142 ms |
| Oct 3, 2026 | 138 ms |
| Oct 10, 2026 | 145 ms |
| Oct 17, 2026 | 163 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
Improve image delivery
1.5 s · 346 KiB7 images could be 346 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.
Mobile performance score: 41
41/100Your mobile performance score is 41 (desktop: 56). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.9 s
A phone's processor spends 6.9 s on main-thread work while loading, 3.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,894 HTML elements
The page has 3,894 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
900 ms · 335 KiBAbout 335 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 1.0 s. During a long task the page ignores taps.
Render-blocking requests
550 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 550 ms.
Reduce unused CSS
450 ms · 63 KiBAbout 63 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
7 third-party services on the page
7 third-party services load with your homepage (Google/Doubleclick Ads, notify-me.io and Shopify and others), adding 448 KiB and 321 ms of main-thread time.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Use efficient cache lifetimes
78 KiB4 files are served with short cache lifetimes, so returning visitors download them again (78 KiB).
Minify CSS
11 KiB11 KiB could be saved by minifying CSS.
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: 12 ms
12 msYour server sent the HTML in 12 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.
Largest Contentful Paint: 7.4 s
7.4 sYour largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (3.1 s).
Speed Index: 9.1 s
9.1 sVisually, the page fills in at 9.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 8.5 s
8.5 sThe page becomes fully interactive after 8.5 s. Good is under 3.8 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 164 ms to 163 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 168 ms
168 msReal visitors wait 168 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.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 730 ms
730 msReal visitors wait 730 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.011
0.011The layout barely moves while loading (CLS 0.011, good is under 0.1).
Images and page weight
Page weight: 2.4 MB in 170 requests
2.4 MBYour homepage downloads 2.4 MB in 170 requests on a phone: other files 807 KiB (103), scripts 678 KiB (39) and images 616 KiB (15). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (157 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.
About 0.7 g of CO₂ per visit
0.68 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.68 g of CO₂e: 81.1 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
Hidden but focusable
24 elements hidden from screen readers can still receive keyboard focus.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Orphan list items
Some list items are not inside a list.
Invalid ARIA attributes
4 elements use ARIA attributes their role does not allow, which confuses screen readers.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
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.
13 links without text
13 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 (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (4 elements).
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 10 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is short (37 characters)
Your meta description is only 37 characters: “دار الفكر المعاصر - بيت الكتاب العربي”. 70 to 160 characters is enough to sell the click.
222 internal links, 21 external
The homepage links to 222 pages on fikr.com and 21 external pages.
6 checks passed
Title: 60 characters
Your title is a healthy 60 characters: “دار الفكر المعاصر _ آفاق معرفة متجددة — DAR ALFIKR ALMOUASER”.
Canonical URL set
The canonical URL is https://fikr.com/.
Structured data in place
Structured data found: WebSite.
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://fikr.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.
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.
llms.txt published
The site publishes https://fikr.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without a meta description
https://fikr.com/pages/contact-us, https://fikr.com/pages/%D8%A7%D9%84%D8%A7%D8%B4%D8%AA%D8%B1%D8%A7%D9%83, https://fikr.com/collections/%D8%A7%D9%84%D9%82%D8%B1%D8%A2%D9%86-%D8%A7%D9%84%D9%83%D8%B1%D9%8A%D9%85-%D9%88%D8%B9%D9%84%D9%88%D9%85%D9%87, https://fikr.com/collections/%D8%A7%D9%84%D8%AD%D8%AF%D9%8A%D8%AB-%D8%A7%D9%84%D8%B4%D8%B1%D9%8A%D9%81-%D9%88%D8%B9%D9%84%D9%88%D9%85%D9%87, https://fikr.com/collections/%D8%A7%D9%84%D8%B9%D9%82%D9%8A%D8%AF%D8%A9-%D9%88%D8%A3%D8%B5%D9%88%D9%84-%D8%A7%D9%84%D8%AF%D9%8A%D9%86 and https://fikr.com/collections/%D8%A7%D9%84%D9%81%D9%82%D9%87-%D8%A7%D9%84%D8%A5%D8%B3%D9%84%D8%A7%D9%85%D9%8A-%D9%88%D8%A3%D8%B5%D9%88%D9%84%D9%87 and 9 others have 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://fikr.com/pages/%D8%A7%D9%84%D8%A7%D8%B4%D8%AA%D8%B1%D8%A7%D9%83, whose canonical is https://fikr.com/pages/%d8%a7%d9%84%d8%a7%d8%b4%d8%aa%d8%b1%d8%a7%d9%83. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://fikr.com/pages/%D8%A7%D9%84%D8%A7%D8%B4%D8%AA%D8%B1%D8%A7%D9%83 has no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://fikr.com/pages/contact-us and https://fikr.com/pages/%D8%A7%D9%84%D8%A7%D8%B4%D8%AA%D8%B1%D8%A7%D9%83 have 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 98 found) and read each the way a search engine does.
4 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.
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
26 small tap targets
26 of 115 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
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.
Thin social proof
Social proof on the homepage: 30 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 145 words
The homepage has only about 145 words of visible text; thin pages give Google and first-time buyers little to go on.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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.
1 checks passed
5 short forms
5 short forms (1 field at most) are right on the homepage.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads 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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
14 other companies contacted
Loading the homepage contacts 14 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 fikr.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on fikr.com, including 15 speed issues, 2 SEO issues and 5 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.