Website review, no card needed
quarafinance.com website review
Visit site (opens in a new tab)Reviewed 30 October 202641 issues · 82 checks
This review found 41 issues worth fixing on quarafinance.com, 21 of them high impact, across 82 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.2 s |
| Oct 24, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Oct 3, 2026 | 122 ms |
| Oct 10, 2026 | 122 ms |
| Oct 17, 2026 | 123 ms |
| Oct 24, 2026 | 124 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
How it loaded on a phone
2.6 s
5.2 s
7.9 s
10.5 s
13.1 s
15.7 s
18.4 s
21.0 s
Speed
Use efficient cache lifetimes
22.3 s · 6.5 MB32 files are served with short cache lifetimes, so returning visitors download them again (6.5 MB).
Improve image delivery
8.7 s · 5.8 MB27 images could be 5.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.7 s faster on a phone.
Reduce unused JavaScript
7.1 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.1 s faster on a phone.
Minify JavaScript
3.7 s · 689 KiB689 KiB could be saved by minifying JavaScript.
Render-blocking requests
2.9 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.9 s.
Document request latency
1.6 s · 302 KiBThe HTML itself could arrive about 1.6 s sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
1.5 sReduce initial server response time. Google estimates savings of 1.5 s on a phone.
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused CSS
780 ms · 129 KiBAbout 129 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 780 ms faster on a phone.
7 third-party services on the page
7 third-party services load with your homepage (unifonic.com, Google Tag Manager and Cloudflare CDN and others), adding 4.3 MB and 471 ms of main-thread time.
unifonic.com adds 290 ms
290 msunifonic.com costs a phone 290 ms of main-thread work and 3.9 MB 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 529 ms. During a long task the page ignores taps.
Google Tag Manager adds 173 ms
173 msGoogle Tag Manager costs a phone 173 ms of main-thread work and 307 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.
Server response: 1.6 s
1.6 sYour server takes 1.6 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
Minify CSS
150 ms · 15 KiB15 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
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 632 ms of it running JavaScript. That is comfortably low.
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 FCP: 3.1 s
3.1 sReal visitors see the first content after 3.1 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 80.5 s
80.5 sYour largest element takes 80.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 23.9 s
23.9 sVisually, the page fills in at 23.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 82.5 s
82.5 sThe page becomes fully interactive after 82.5 s. Good is under 3.8 s.
First Contentful Paint: 6.0 s
6.0 sThe first text or image appears after 6.0 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.9 s
3.9 sReal visitors wait 3.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user TTFB: 882 ms
882 msReal visitors wait 882 ms for your server to start answering (75th percentile). Good is under 800 ms.
38 images without width and height
38 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 449 ms
449 msScripts block taps and scrolling for 449 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 122 ms to 124 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.5 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 113 ms
113 msReal visitors wait 113 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.
Cumulative Layout Shift: 0.009
0.009The layout barely moves while loading (CLS 0.009, good is under 0.1).
Images and page weight
Page weight: 16.5 MB in 98 requests
16.5 MBYour homepage downloads 16.5 MB in 98 requests on a phone: images 11.4 MB (55), scripts 4.2 MB (15) and HTML 452 KiB (1). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 6.4 MB together. On a phone connection a single image that size takes seconds.
8 images far larger than shown
1.5 MB8 images are downloaded at several times the size a phone draws them, for example hero_banner_ar.gif at 1,356 px wide, shown at 358 px. Resized copies would save about 1.5 MB.
8 images in older formats
8 images (7.2 MB) 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.
An image on the first screen is lazy-loaded
hero_banner_ar.gif 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).
1 image below the first screen load straight away
1 image further down the page (30 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 4.7 g of CO₂ per visit
4.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.67 g of CO₂e: 559.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
2 checks passed
Every image has alt text
All 73 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 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 1 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
50 internal links, 14 external
The homepage links to 50 pages on quarafinance.com and 14 external pages.
7 checks passed
Meta description: 133 characters
Your meta description is 133 characters: “احصل على تمويل شخصي أون لاين بسهولة وسرعة مع كوارا. شركات التمويل الشخصي الموثوقة لتمويل الأفراد في السعودية بموافقة فو…”.
One H1 headline
Your main headline reads: “حريتك المالية تبدأ من هنا”.
Title: 51 characters
Your title is a healthy 51 characters: “تمويل شخصي سريع للأفراد في السعودية | كوارا للتمويل”.
Canonical URL set
The canonical URL is https://quarafinance.com.sa/ar/.
Structured data in place
Structured data found: CollectionPage, Organization and WebSite.
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://quarafinance.com.sa/apple/sitemap.xml.
AI search readiness
3 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
llms.txt published
The site publishes https://quarafinance.com.sa/llms.txt (2 KiB, 24 links), a plain-text guide to the site for AI tools.
Other pages
4 pages share 2 titles
https://quarafinance.com.sa/ar/naqdi and https://quarafinance.com.sa/naqdi all use the title “تمويل نقدي سريع للأفراد في السعودية | كوارا للتمويل”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages share a meta description
https://quarafinance.com.sa/ar/naqdi and https://quarafinance.com.sa/naqdi use the same meta description. A description written for each page earns more clicks.
8 links to non-canonical URLs
Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://quarafinance.com.sa/sharia, whose canonical is https://quarafinance.com.sa/ar/sharia. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
10 pages with very little text
https://quarafinance.com.sa/ar/about-us, https://quarafinance.com.sa/ar/naqdi, https://quarafinance.com.sa/ar/tasawwaq, https://quarafinance.com.sa/ar/payment-methods, https://quarafinance.com.sa/ar/contact-general-inquiries and https://quarafinance.com.sa/ar/partners and 4 others 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.
2 pages slow to respond
https://quarafinance.com.sa/news and https://quarafinance.com.sa/news/personal-loan-of-up-to-sar-50000-in-saudi-arabia took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 28 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
1 broken image
1 image failed to load on a phone, for example https://quarafinance.com.sa/ar/.
1 small tap target
1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 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 59 words
The homepage has only about 59 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.
2 checks passed
Social proof on the page
Social proof on the homepage: 10 testimonial or review blocks and 7 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, 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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
6 other companies contacted
Loading the homepage contacts 6 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 quarafinance.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- Tailwind CSS
- Analytics
- Google Tag Manager
- Hosting
- Nournet
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 quarafinance.com, including 24 speed issues, 1 SEO issue 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.