Website review, no card needed

technos.co logo

technos.co website review

Visit site (opens in a new tab)Reviewed 19 November 202637 issues · 67 checks

This review found 37 issues worth fixing on technos.co, 11 of them high impact, across 67 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of technos.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. technos.co at 0.9 s0.9 s
  2. technos.co at 1.7 s1.7 s
  3. technos.co at 2.6 s2.6 s
  4. technos.co at 3.4 s3.4 s
  5. technos.co at 4.3 s4.3 s
  6. technos.co at 5.1 s5.1 s
  7. technos.co at 6.0 s6.0 s
  8. technos.co at 6.8 s6.8 s

Speed

10 to fix58
  • Reduce unused JavaScript

    3.2 s · 606 KiB

    About 606 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.2 s faster on a phone.

  • Render-blocking requests

    2.4 s

    25 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.

  • Use efficient cache lifetimes

    1.6 s · 336 KiB

    34 files are served with short cache lifetimes, so returning visitors download them again (336 KiB).

  • Mobile performance score: 58

    58/100

    Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.

  • 5 long tasks on the main thread

    5 long tasks block the main thread while loading, the longest for 895 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    600 ms · 138 KiB

    About 138 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • 5 third-party services on the page

    5 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and Google Fonts and others), adding 1.1 MB and 446 ms of main-thread time.

  • YouTube adds 436 ms

    436 ms

    YouTube costs a phone 436 ms of main-thread work and 1,019 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.

  • Improve image delivery

    300 ms · 202 KiB

    9 images could be 202 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Main-thread work: 2.3 s

    A phone's processor spends 2.3 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Minify JavaScript

    150 ms · 32 KiB

    32 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    100 ms · 8 KiB

    Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

  • Document request latency

    10 KiB

    The 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.

1 checks passed
  • Server response: 184 ms

    184 ms

    Your server sent the HTML in 184 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix66
  • Largest Contentful Paint: 14.6 s

    14.6 s

    Your largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your Intelligent Project Partners”.

  • Speed Index: 12.3 s

    12.3 s

    Visually, the page fills in at 12.3 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 14.8 s

    14.8 s

    The page becomes fully interactive after 14.8 s. Good is under 3.8 s.

  • First Contentful Paint: 3.8 s

    3.8 s

    The first text or image appears after 3.8 s on a phone. Good is under 1.8 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.

2 checks passed
  • Total Blocking Time: 91 ms

    91 ms

    Scripts block the page for only 91 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 2.5 MB in 80 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 80 requests on a phone: scripts 1.1 MB (25), images 1.1 MB (16) and stylesheets 131 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.70 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.70 g of CO₂e: 84.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

5 to fixGoogle 8090
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails 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.

  • 3 text elements with low contrast

    3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

2 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 29 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 33 WCAG 2.2 A/AA and best-practice rules on the phone render: 29 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 9164
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (7 characters)

    Your title is only 7 characters: “TECHNOS”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 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://technos.co/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at technos.co/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 29 internal links, 2 external

    The homepage links to 29 pages on technos.co and 2 external pages.

1 checks passed
  • One H1 headline

    Your main headline reads: “TECHNOS”.

AI search readiness

1 to fix88
  • 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 https://technos.co/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 (186 words), so crawlers that don't run JavaScript still read it.

Best practices

4 to fixGoogle 3383
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 small tap targets

    3 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'innerHTML')”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix60
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 152 words

    The homepage has only about 152 words of visible text; thin pages give Google and first-time buyers little to go on.

  • 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 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
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Us” and “Inquire”.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Ads (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.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies, 1 of them by other companies (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 technos.co, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2016.

Stack

Framework
jQuery
Hosting
SK Broadband Co Ltd

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 technos.co, including 15 speed issues, 7 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25