Website review, no card needed

7t.co logo

7t.co website review

Visit site (opens in a new tab)Reviewed 16 November 202630 issues · 84 checks

This review found 30 issues worth fixing on 7t.co, 11 of them high impact, across 84 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 7t.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 7t.co at 0.4 s0.4 s
  2. 7t.co at 0.8 s0.8 s
  3. 7t.co at 1.2 s1.2 s
  4. 7t.co at 1.6 s1.6 s
  5. 7t.co at 2.1 s2.1 s
  6. 7t.co at 2.5 s2.5 s
  7. 7t.co at 2.9 s2.9 s
  8. 7t.co at 3.3 s3.3 s

Speed

10 to fix49
  • Reduce unused JavaScript

    8.0 s · 1.5 MB

    About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.0 s faster on a phone.

  • Improve image delivery

    2.1 s · 679 KiB

    4 images could be 679 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

  • Render-blocking requests

    2.4 s

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

  • Mobile performance score: 49

    49/100

    Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 2.8 MB and 1.2 s of main-thread time.

  • Reduce unused CSS

    900 ms · 145 KiB

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

  • Google CDN adds 630 ms

    630 ms

    Google CDN costs a phone 630 ms of main-thread work and 1.9 MB 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.

  • Google Tag Manager adds 445 ms

    445 ms

    Google Tag Manager costs a phone 445 ms of main-thread work and 838 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.

  • Main-thread work: 3.9 s

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

  • 1,935 HTML elements

    The page has 1,935 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 17 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Use efficient cache lifetimes

    26 KiB

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

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 6 ms

    6 ms

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

Core Web Vitals

6 to fix59
  • First Contentful Paint: 10.2 s

    10.2 s

    The first text or image appears after 10.2 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 21.0 s

    21.0 s

    Your largest element takes 21.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 26.2 s

    26.2 s

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

  • Speed Index: 10.2 s

    10.2 s

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

  • Total Blocking Time: 302 ms

    302 ms

    Scripts block taps and scrolling for 302 ms in total while the page loads. Good is under 200 ms.

  • 6 images without width and height

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

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 5.7 MB in 154 requests

    5.7 MB

    Your homepage downloads 5.7 MB in 154 requests on a phone: scripts 2.9 MB (48), images 1.3 MB (33) and other files 718 KiB (20). Under 2 MB keeps phones on slow connections fast.

  • About 1.6 g of CO₂ per visit

    1.61 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.61 g of CO₂e: 193.2 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

8 to fixGoogle 8791
  • 5 buttons without a name

    5 buttons have no accessible name, so screen readers announce just “button”.

  • 33 text elements with low contrast

    33 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 (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 14 form fields without a label

    14 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 62 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

1 to fixGoogle 9298
  • 22 links with vague text

    22 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 122 internal links, 7 external

    The homepage links to 122 pages on 7t.co and 7 external pages.

8 checks passed
  • Meta description: 134 characters

    Your meta description is 134 characters: “Custom agentic AI solutions built for your business. 7T embeds AI into existing systems, workflows, and operations for …”.

  • One H1 headline

    Your main headline reads: “Custom Agentic AI Solutions”.

  • Title: 32 characters

    Your title is a healthy 32 characters: “Custom Agentic AI Solutions | 7T”.

  • Canonical URL set

    The canonical URL is https://7t.ai/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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://7t.ai/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://7t.ai/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

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,268 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 8 pages without an H1

    https://7t.ai/accelerate-growth/ai-consulting-services-7tt, https://7t.ai/accelerate-growth/ai-agent-development-services, https://7t.ai/accelerate-growth/digital-transformation-7tt, https://7t.ai/accelerate-growth/erp-crm-consulting-services, https://7t.ai/accelerate-growth/gis-geospatial-solutions and https://7t.ai/accelerate-growth/enterprise-integration-services-7tt and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 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

1 to fixGoogle 9293
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “wp is not defined”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    17 of 21 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 2,720 words of copy

    The homepage carries about 2,720 words of visible text.

7 checks passed
  • Clear next step on the first screen

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

  • 16 calls to action

    The homepage has 16 calls to action, for example “Contact”, “Learn More” and “Learn more”.

  • 2 short forms

    2 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 65 testimonial or review blocks and 4 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

    7

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

  • 16 other companies contacted

    Loading the homepage contacts 16 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 7t.co, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on 7t.co, including 16 speed issues, 1 SEO issue and 1 conversion gap. 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