Website review, no card needed
triyoginnovation.com website review
Visit site (opens in a new tab)Reviewed 10 November 202633 issues · 80 checks
This review found 33 issues worth fixing on triyoginnovation.com, 13 of them high impact, across 80 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
76CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.1 s
2.1 s
3.1 s
4.2 s
5.2 s
6.3 s
7.3 s
8.4 s
Speed
Use efficient cache lifetimes
35.3 s · 23.7 MB57 files are served with short cache lifetimes, so returning visitors download them again (23.7 MB).
Improve image delivery
23.8 s · 19.0 MB21 images could be 19.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 23.8 s faster on a phone.
Render-blocking requests
8.2 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 8.2 s.
Reduce unused CSS
5.9 s · 958 KiBAbout 958 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 5.9 s faster on a phone.
Reduce unused JavaScript
1.5 s · 866 KiBAbout 866 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Minify CSS
750 ms · 135 KiB135 KiB could be saved by minifying CSS.
Font display
500 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 500 ms).
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 113 ms. During a long task the page ignores taps.
2 third-party services on the page
2 third-party services load with your homepage (azure.com and Google Fonts), adding 142 KiB and 80 ms of main-thread time.
Minify JavaScript
56 KiB56 KiB could be saved by minifying JavaScript.
Document request latency
49 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 674 ms of it running JavaScript. That is comfortably low.
Server response: 492 ms
492 msYour server sent the HTML in 492 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 42.3 s
42.3 sYour largest element takes 42.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SPECIALIST ICT FOR GOVERNMENT & DEVELOPMENT Intelligent Ins…”.
Speed Index: 24.9 s
24.9 sVisually, the page fills in at 24.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 42.6 s
42.6 sThe page becomes fully interactive after 42.6 s. Good is under 3.8 s.
30 images without width and height
30 images 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.
2 checks passed
Cumulative Layout Shift: 0.082
0.082The layout barely moves while loading (CLS 0.082, good is under 0.1).
Total Blocking Time: 32 ms
32 msScripts block the page for only 32 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 23.9 MB in 66 requests
23.9 MBYour homepage downloads 23.9 MB in 66 requests on a phone: images 21.3 MB (34), scripts 1.2 MB (6) and stylesheets 1,000 KiB (17). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 4.4 MB together. On a phone connection a single image that size takes seconds.
2 images far larger than shown
1.5 MB2 images are downloaded at several times the size a phone draws them, for example 7a5070a5-fd76-4838-915c-a2eb7d473f59_ChatGPT Image Mar 3, 20 at 1,536 px wide, shown at 344 px. Resized copies would save about 1.5 MB.
5 images in older formats
5 images (4.7 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.
4 images below the first screen load straight away
4 images further down the page (4.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 6.8 g of CO₂ per visit
6.78 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.78 g of CO₂e: 813.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
16 text elements with low contrast
16 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 (9 elements)
All page content should be contained by landmarks: 9 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 (h1 → h5, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 6 images in the HTML carry an alt attribute.
25 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 30 WCAG 2.2 A/AA and best-practice rules on the phone render: 25 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (135 characters)
Your title is 135 characters, so Google will cut it off around 60: “Triyog Innovations | Institutional Digital Systems for Africa & Asia | Transport · En…”.
Meta description is long (268 characters)
Your meta description is 268 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization and Service) but with 1 problem, for example “Service: no offers (price) block”.
No robots.txt
There is no robots.txt at triyoginnovation.com/robots.txt, the first file search crawlers ask for.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
39 internal links, 2 external
The homepage links to 39 pages on triyoginnovation.com and 2 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Intelligent Institutional Digital Systems Across Africa & Asia”.
Canonical URL set
The canonical URL is https://triyoginnovation.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
XML sitemap found
Your XML sitemap is reachable at https://triyoginnovation.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://triyoginnovation.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.
3 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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (835 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://triyoginnovation.com/org-chart has no meta description, so Google writes the search snippet from whatever text it finds.
10 pages without an H1
https://triyoginnovation.com/about, https://triyoginnovation.com/org-chart, https://triyoginnovation.com/our-sectors, https://triyoginnovation.com/sector/ICT, https://triyoginnovation.com/sector/education and https://triyoginnovation.com/sector/transport and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://triyoginnovation.com/org-chart has 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 26 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
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)”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 956 words of copy
The homepage carries about 956 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SCHEDULE A CONSULTATION”.
3 calls to action
The homepage has 3 calls to action, for example “Contact” and “Schedule a Consultation”.
Social proof on the page
Social proof on the homepage: 1 trust badge and “15+ Clients”.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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).
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 triyoginnovation.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Hosting
- Azure
Hiring
- Hiring
- 4 open roles
- Job board
- careers page
- Careers page
- triyoginnovation.com/career (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on triyoginnovation.com, including 13 speed issues, 5 SEO issues and 2 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.