Website review, no card needed
appsouls.com website review
Visit site (opens in a new tab)Reviewed 8 November 202643 issues · 84 checks
This review found 43 issues worth fixing on appsouls.com, 11 of them high impact, across 84 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
67DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
appsouls.com does not allow embedding, so this is Google's rendering of the page.
Speed
Improve image delivery
3.4 s · 1.1 MB14 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.4 s faster on a phone.
Use efficient cache lifetimes
800 ms · 202 KiB25 files are served with short cache lifetimes, so returning visitors download them again (202 KiB).
Mobile performance score: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Reduce unused JavaScript
80 ms · 21 KiBAbout 21 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 80 ms faster on a phone.
Reduce unused CSS
80 ms · 17 KiBAbout 17 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 80 ms faster on a phone.
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.
2 checks passed
Main-thread work: 0.1 s
A phone's processor spends 0.1 s on main-thread work while loading, 23 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.6 s
8.6 sYour largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Try Demo”.
Time to Interactive: 8.8 s
8.8 sThe page becomes fully interactive after 8.8 s. Good is under 3.8 s.
Speed Index: 4.2 s
4.2 sVisually, the page fills in at 4.2 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
3 checks passed
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
10 images below the first screen load straight away
10 images further down the page (493 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
4 images far larger than shown
155 KiB4 images are downloaded at several times the size a phone draws them, for example administration_control.jpg at 519 px wide, shown at 100 px. Resized copies would save about 155 KiB.
8 images in older formats
8 images (418 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.5 g of CO₂ per visit
0.46 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.46 g of CO₂e: 54.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.6 MB in 26 requests
1.6 MBYour homepage downloads 1.6 MB in 26 requests on a phone: images 1.5 MB (21), scripts 42 KiB (2) and stylesheets 20 KiB (2). That is a lean page.
Accessibility
Orphan list items
Some list items are not inside a list.
Links look like plain text
11 links inside paragraphs rely on colour alone to stand out.
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
13 images without alt text
13 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h4 and h1 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
28 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 28 passed and 9 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 long (110 characters)
Your title is 110 characters, so Google will cut it off around 60: “Software Solutions, Business Automation Solution, Blockchain Development, IOT Platform, T…”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
3 H1 headlines
There are 3 <h1> headlines (“Apply intelligence with Appsouls ERP”, “Key Functions” and “Embracing the Future”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (232 characters)
Your meta description is 232 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at http://appsouls.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at appsouls.com/robots.txt, the first file search crawlers ask for.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
52 internal links, 3 external
The homepage links to 52 pages on appsouls.com and 3 external pages.
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.
No llms.txt
There is no /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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,209 words), so crawlers that don't run JavaScript still read it.
Other pages
9 linked pages are broken
Your homepage links to /pages/products/hybridex.php, /pages/products/wallet.php, /pages/products/blockchain.php, /pages/products/vault.php, /pages/products/appnode.php and /pages/products/appnode-light.php and 3 others, which answer with an error. Visitors hit a dead end and search engines drop them.
4 pages share a title
/pages/solutions/asset-management.php, /pages/solutions/manufacturing.php, /pages/solutions/financial-institutes.php and /pages/solutions/human-resource-management.php all use the title “Appsoules Technologies Limited | Software Solutions | Business Automa…”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
/solutions.php has no meta description, so Google writes the search snippet from whatever text it finds.
5 pages share a meta description
/pages/products/iot-connected-erp.php, /pages/solutions/asset-management.php, /pages/solutions/manufacturing.php, /pages/solutions/financial-institutes.php and /pages/solutions/human-resource-management.php use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 40 found) and read each the way a search engine does.
4 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 6 pages that loaded have a <title>.
Best practices
4 small tap targets
4 of 7 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 (Not Found)”.
9 distorted images
9 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Does not redirect HTTP traffic to HTTPS
Does not redirect HTTP traffic to HTTPS.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Security and trust
No HTTPS
Your homepage is served without HTTPS, so browsers mark it “Not secure” and some refuse forms on it.
15 broken links to your own pages
15 links from your homepage to your own site are broken, for example http://www.appsouls.com/pages/products/hybridex.php (404).
http:// does not redirect
http://appsouls.com does not redirect to https, so some visitors land on the insecure version.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
Domain and trust
Domain expires in 62 days
appsouls.com is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.
No CAA record
appsouls.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
DNSSEC is off
appsouls.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.
1 checks passed
Domain is 2 years old
2 yearsappsouls.com was registered in Jan 2024 through NameCheap, Inc.. An established domain carries more trust with email providers and search engines.
Content and conversion
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
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.
About 1,123 words of copy
The homepage carries about 1,123 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Try Demo”.
3 calls to action
The homepage has 3 calls to action, for example “Contact Us”, “Apply Now” and “Try Demo”.
Email authentication
DMARC is monitor-only (p=none)
DMARC is set to p=none, so mail pretending to be appsouls.com is still delivered. Add a report address, check the reports, then move to quarantine.
Email authentication score: 70/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
2 checks passed
SPF in place (~all)
An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 +a +mx +ip4:198.54.114.127 include:spf.web-hosting.com ~all”.
DKIM signing found
A DKIM key is published (selector “default”), so receivers can verify mail really came from you.
Privacy and tracking
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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Upkeep, stack and company
Stack
- Framework
- jQuery
- Hosting
- Namecheap
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on appsouls.com, including 8 speed issues, 9 SEO issues and 3 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.