Website review, no card needed
yemensoft.com website review
Visit site (opens in a new tab)Reviewed 30 October 202637 issues · 83 checks
This review found 37 issues worth fixing on yemensoft.com, 21 of them high impact, across 83 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
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 9.0 s |
| May 16, 2026 | 9.6 s |
| May 23, 2026 | 9.7 s |
| May 30, 2026 | 10.1 s |
| Jun 20, 2026 | 8.4 s |
| Jun 27, 2026 | 8.0 s |
| Jul 4, 2026 | 7.9 s |
| Jul 11, 2026 | 7.9 s |
| Jul 18, 2026 | 7.7 s |
| Jul 25, 2026 | 8.1 s |
| Aug 1, 2026 | 8.3 s |
| Aug 8, 2026 | 8.4 s |
| Aug 15, 2026 | 8.9 s |
| Aug 22, 2026 | 8.8 s |
| Aug 29, 2026 | 9.1 s |
| Sep 5, 2026 | 9.7 s |
| Sep 12, 2026 | 9.4 s |
| Sep 19, 2026 | 9.3 s |
| Sep 26, 2026 | 10.0 s |
| Oct 3, 2026 | 9.6 s |
| Oct 10, 2026 | 9.4 s |
| Oct 17, 2026 | 8.7 s |
| Oct 24, 2026 | 8.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 157 ms |
| May 16, 2026 | 149 ms |
| May 23, 2026 | 152 ms |
| May 30, 2026 | 188 ms |
| Jun 20, 2026 | 181 ms |
| Jun 27, 2026 | 158 ms |
| Jul 4, 2026 | 161 ms |
| Jul 11, 2026 | 170 ms |
| Jul 18, 2026 | 175 ms |
| Jul 25, 2026 | 181 ms |
| Aug 1, 2026 | 187 ms |
| Aug 8, 2026 | 184 ms |
| Aug 15, 2026 | 187 ms |
| Aug 22, 2026 | 177 ms |
| Aug 29, 2026 | 188 ms |
| Sep 5, 2026 | 194 ms |
| Sep 12, 2026 | 182 ms |
| Sep 19, 2026 | 185 ms |
| Sep 26, 2026 | 172 ms |
| Oct 3, 2026 | 171 ms |
| Oct 10, 2026 | 181 ms |
| Oct 17, 2026 | 180 ms |
| Oct 24, 2026 | 179 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
21.3 s · 14.3 MB117 files are served with short cache lifetimes, so returning visitors download them again (14.3 MB).
Render-blocking requests
7.2 s50 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.2 s.
Reduce unused JavaScript
4.0 s · 759 KiBAbout 759 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.
Reduce unused CSS
3.3 s · 705 KiBAbout 705 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.3 s faster on a phone.
Improve image delivery
3.1 s · 556 KiB10 images could be 556 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.1 s faster on a phone.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Document request latency
311 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
1,548 HTML elements
The page has 1,548 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify CSS
150 ms · 53 KiB53 KiB could be saved by minifying CSS.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Clarity and Google Fonts and others), adding 297 KiB and 135 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 55 ms. During a long task the page ignores taps.
Legacy JavaScript
30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need.
Minify JavaScript
11 KiB11 KiB could be saved by minifying JavaScript.
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.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 467 ms of it running JavaScript. That is comfortably low.
Server response: 138 ms
138 msYour server sent the HTML in 138 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: 12.3 s
12.3 sReal visitors wait 12.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 7.8 s
7.8 sReal visitors see the first content after 7.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.6 s
2.6 sReal visitors wait 2.6 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 8.5 s
8.5 sThe first text or image appears after 8.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 27.8 s
27.8 sYour largest element takes 27.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 27.9 s
27.9 sThe page becomes fully interactive after 27.9 s. Good is under 3.8 s.
Speed Index: 14.8 s
14.8 sVisually, the page fills in at 14.8 s (Speed Index). Good is under 3.4 s.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 157 ms to 179 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 9.0 s to 8.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
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.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Total Blocking Time: 5 ms
5 msScripts block the page for only 5 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 15.1 MB in 138 requests
15.1 MBYour homepage downloads 15.1 MB in 138 requests on a phone: images 12.1 MB (40), scripts 1.5 MB (41) and stylesheets 833 KiB (44). Under 2 MB keeps phones on slow connections fast.
9 images over 500 KB
9 images weigh 10.2 MB together. On a phone connection a single image that size takes seconds.
11 images far larger than shown
2.6 MB11 images are downloaded at several times the size a phone draws them, for example 01.png at 2,025 px wide, shown at 360 px. Resized copies would save about 2.6 MB.
21 images in older formats
21 images (11.0 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.
10 images below the first screen load straight away
10 images further down the page (10.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.3 g of CO₂ per visit
4.27 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.27 g of CO₂e: 512.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
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.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious 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.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 90 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 failed. 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.
Title is short (19 characters)
Your title is only 19 characters: “الرئيسية | يمن سوفت”. Between 30 and 65 characters leaves room to say what you do and for whom.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
116 internal links, 19 external
The homepage links to 116 pages on yemensoft.com and 19 external pages.
6 checks passed
Meta description: 127 characters
Your meta description is 127 characters: “شركة وطنية وإقليمية رائدة في مجال إنشاء وتطوير الحلول البرمجية المالية والإدارية لمختلف قطاعات الأعمال في السوق المحلي …”.
Canonical URL set
The canonical URL is https://yemensoft.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and 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://yemensoft.com/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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
llms.txt published
The site publishes https://yemensoft.com/llms.txt (142 KiB, 403 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
15 pages without an H1
https://yemensoft.com/ar-about-us, https://yemensoft.com/ar-yemensoft-solutions, https://yemensoft.com/ar-human-recourse-management-solution, https://yemensoft.com/ar-motakamel-pro-system, https://yemensoft.com/ar-motakamel-silver-system and https://yemensoft.com/ar-motakamel-plus-erp-solutions and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 pages with very little text
https://yemensoft.com/ar-about-us, https://yemensoft.com/ar-yemensoft-solutions, https://yemensoft.com/ar-human-recourse-management-solution, https://yemensoft.com/ar-motakamel-pro-system, https://yemensoft.com/ar-motakamel-silver-system and https://yemensoft.com/ar-motakamel-plus-erp-solutions and 9 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.
4 pages slow to respond
https://yemensoft.com/ar-onyx-erp-solutions, https://yemensoft.com/ar-restaurant-management-system-ferp, https://yemensoft.com/ar-hotel-management-system and https://yemensoft.com/ar-gold-operations-management-system-erp took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 42 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 distorted images
10 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
34 of 37 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.
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 38 words
The homepage has only about 38 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.
1 checks passed
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Microsoft Clarity (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.
11 other companies contacted
Loading the homepage contacts 11 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 yemensoft.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
- jQuery
- Analytics
- Google Analytics | Microsoft Clarity
- Hosting
- Oracle Cloud
Company
- Founded
- 1993
- Headquarters
- Sanaa
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on yemensoft.com, including 17 speed issues, 3 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.