Website review, no card needed
aitacs.com website review
Visit site (opens in a new tab)Reviewed 18 October 202634 issues · 83 checks
This review found 34 issues worth fixing on aitacs.com, 11 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
72CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
4.0 s · 1.1 MB104 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
Render-blocking requests
4.1 s36 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.1 s.
3,176 HTML elements
The page has 3,176 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 54
54/100Your mobile performance score is 54 (desktop: 81). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 123 KiBAbout 123 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 326 ms
326 msGoogle Tag Manager costs a phone 326 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.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 336 ms. During a long task the page ignores taps.
Reduce unused JavaScript
310 KiBAbout 310 KiB of JavaScript is downloaded but never used on this page.
Improve image delivery
250 ms · 144 KiB11 images could be 144 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, cdn-cookieyes.com and Google Fonts and others), adding 432 KiB and 326 ms of main-thread time.
Minify CSS
150 ms · 14 KiB14 KiB could be saved by minifying CSS.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Phones get a much slower page than desktops
Desktop scores 81 but mobile only 54. A gap that wide usually means heavy scripts and images that hit phones hardest.
Minify JavaScript
7 KiB7 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.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.0 s
8.0 sYour largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We Help Businesses Create Exceptional and Orchestrated Cust…”. Most of its time is element render delay (3.5 s).
First Contentful Paint: 4.5 s
4.5 sThe first text or image appears after 4.5 s on a phone. Good is under 1.8 s.
Speed Index: 8.9 s
8.9 sVisually, the page fills in at 8.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 8.1 s
8.1 sThe page becomes fully interactive after 8.1 s. Good is under 3.8 s.
Total Blocking Time: 253 ms
253 msScripts block taps and scrolling for 253 ms in total while the page loads. Good is under 200 ms.
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.
1 checks passed
Cumulative Layout Shift: 0.014
0.014The layout barely moves while loading (CLS 0.014, good is under 0.1).
Images and page weight
3 images in older formats
3 images (155 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.4 g of CO₂ per visit
0.45 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.45 g of CO₂e: 53.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.6 MB in 122 requests
1.6 MBYour homepage downloads 1.6 MB in 122 requests on a phone: scripts 514 KiB (40), images 503 KiB (37) and fonts 364 KiB (7). That is a lean page.
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
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
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.
All page content should be contained by landmarks (14 elements)
All page content should be contained by landmarks: 14 elements on the page fail 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.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (4 elements)
Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h6, h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 124 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 7 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.
130 links with vague text
130 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Title is short (18 characters)
Your title is only 18 characters: “Home Page - AITACS”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (27 characters)
Your meta description is only 27 characters: “We Are Digital Changemakers”. 70 to 160 characters is enough to sell the click.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
271 internal links, 4 external
The homepage links to 271 pages on aitacs.com and 4 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.aitacs.com/.
Structured data in place
Structured data found: Article, 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://www.aitacs.com/sitemap_index.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing url, 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://www.aitacs.com/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,117 words), so crawlers that don't run JavaScript still read it.
Other pages
9 pages share a meta description
https://www.aitacs.com/digital-transformation-services, https://www.aitacs.com/sustainability-solutions, https://www.aitacs.com/custom-mobile-app-development-services, https://www.aitacs.com/legacy-modernization-services, https://www.aitacs.com/erp-consulting-services and https://www.aitacs.com/intelligent-automation-solutions and 3 others use the same meta description. A description written for each page earns more clicks.
10 pages without an H1
https://www.aitacs.com/digital-transformation-services, https://www.aitacs.com/salesforce-development-services, https://www.aitacs.com/sustainability-solutions, https://www.aitacs.com/custom-mobile-app-development-services, https://www.aitacs.com/legacy-modernization-services and https://www.aitacs.com/erp-consulting-services and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
12 pages slow to respond
https://www.aitacs.com/pharma-healthcare-staffing, https://www.aitacs.com/msp-vms-staffing, https://www.aitacs.com/digital-transformation-services, https://www.aitacs.com/salesforce-development-services, https://www.aitacs.com/sustainability-solutions and https://www.aitacs.com/custom-mobile-app-development-services and 6 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 126 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
7 small tap targets
7 of 10 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 403 ()”.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 3 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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,650 words of copy
The homepage carries about 1,650 words of visible text.
4 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact Us”, “Download Brochure” and “Get In Touch Now”.
2 short forms
2 short forms (3 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and HubSpot.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
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 aitacs.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 | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on aitacs.com, including 14 speed issues, 5 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.