Website review, no card needed

2itesting.com logo

2itesting.com website review

Visit site (opens in a new tab)Reviewed 3 November 202628 issues · 101 checks

This review found 28 issues worth fixing on 2itesting.com, 4 of them high impact, across 101 checks. The most urgent: render-blocking requests. 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

Real-visitor load time (LCP)75th percentile, phones
1.3 s361 msMay 16Oct 31844 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026679 ms
May 23, 2026608 ms
May 30, 2026574 ms
Jun 6, 2026579 ms
Jun 13, 2026465 ms
Jul 25, 2026794 ms
Aug 1, 2026879 ms
Aug 8, 20261.0 s
Aug 15, 20261.1 s
Aug 22, 20261.2 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 2026950 ms
Sep 19, 2026921 ms
Sep 26, 2026934 ms
Oct 3, 2026959 ms
Oct 10, 20261.0 s
Oct 17, 2026969 ms
Oct 24, 2026921 ms
Oct 31, 2026844 ms
Real-visitor tap response (INP)75th percentile, phones
116 ms72 msMay 16Oct 3187 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026111 ms
May 23, 2026105 ms
May 30, 202695 ms
Jun 6, 202694 ms
Aug 1, 202687 ms
Aug 8, 202687 ms
Aug 15, 202687 ms
Aug 22, 202687 ms
Aug 29, 202684 ms
Sep 5, 202679 ms
Sep 12, 202678 ms
Sep 19, 202677 ms
Sep 26, 202680 ms
Oct 3, 202684 ms
Oct 10, 202683 ms
Oct 17, 202684 ms
Oct 24, 202685 ms
Oct 31, 202687 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of 2itesting.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 2itesting.com at 0.4 s0.4 s
  2. 2itesting.com at 0.8 s0.8 s
  3. 2itesting.com at 1.1 s1.1 s
  4. 2itesting.com at 1.5 s1.5 s
  5. 2itesting.com at 1.9 s1.9 s
  6. 2itesting.com at 2.3 s2.3 s
  7. 2itesting.com at 2.6 s2.6 s
  8. 2itesting.com at 3.0 s3.0 s

2itesting.com does not allow embedding, so this is Google's rendering of the page.

Speed

5 to fix88
  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 88

    88/100

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

  • Use efficient cache lifetimes

    413 KiB

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

  • Google Tag Manager adds 336 ms

    336 ms

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

    373 KiB

    14 images could be 373 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Cookie-Script.com and Hubspot and others), adding 880 KiB and 492 ms of main-thread time.

  • Reduce unused JavaScript

    218 KiB

    About 218 KiB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    140 ms · 47 KiB

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

  • 6 long tasks on the main thread

    6 long tasks block the main thread while loading, the longest for 127 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).

  • Legacy JavaScript

    18 KiB

    Polyfills for old browsers add 18 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 CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.4 s

    A phone's processor spends 1.4 s on main-thread work while loading, 646 ms of it running JavaScript. That is comfortably low.

  • Server response: 99 ms

    99 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 10.0 s

    10.0 s

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

  • Largest content (LCP) got 37% slower for real visitors

    +37%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.7 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.193

    0.193

    The layout shifts by 0.193 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 32 images without width and height

    32 images have no width and height attributes, so the layout jumps as each one loads.

  • First Contentful Paint: 1.8 s

    1.8 s

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

10 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 0.9 s

    0.9 s

    Real visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 87 ms

    87 ms

    Real visitors wait 87 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.8 s

    0.8 s

    Real visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 429 ms

    429 ms

    Real visitors wait 429 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 20% faster for real visitors

    -20%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 111 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Speed Index: 3.1 s

    3.1 s

    Visually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 116 ms

    116 ms

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

  • Largest Contentful Paint: 1.8 s

    1.8 s

    Your largest element renders in 1.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “AI is speeding up change across your business, and new risk…”.

Images and page weight

2 to fix83
  • 2 images far larger than shown

    94 KiB

    2 images are downloaded at several times the size a phone draws them, for example 2i-homepage-people.webp at 960 px wide, shown at 268 px. Resized copies would save about 94 KiB.

  • 4 images below the first screen load straight away

    4 images further down the page (350 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.5 g of CO₂ per visit

    0.50 g

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

2 checks passed
  • Page weight: 1.8 MB in 70 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 70 requests on a phone: images 851 KiB (44), scripts 678 KiB (11) and fonts 184 KiB (3). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

3 to fixGoogle 9697
  • All page content should be contained by landmarks (28 elements)

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 74 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

5 to fixGoogle 9280
  • 2 H1 headlines

    There are 2 <h1> headlines (“2i. We test. You impress” and “Quality Intelligence is here.”). One clear main headline is easier for people and search engines.

  • Meta description is long (299 characters)

    Your meta description is 299 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("SearchPageUrl")”.

  • No XML sitemap

    No XML sitemap at https://2itesting.com/sitemap.xml, so Google discovers your pages only by following links.

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

  • 36 internal links, 4 external

    The homepage links to 36 pages on 2itesting.com and 4 external pages.

4 checks passed
  • Title: 57 characters

    Your title is a healthy 57 characters: “2i | Independent QA & Software Testing for Complex Change”.

  • Canonical URL set

    The canonical URL is https://2itesting.com/.

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

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, 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 /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 (955 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 1 linked page hidden from search

    /about-us/environmental-social-governance is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    /about-us/environmental-social-governance has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 27 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.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10078
  • 1 broken image

    1 image failed to load on a phone, for example https://2itesting.com/.

  • 3 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • Short HSTS lifetime

    HSTS is set, but max-age is 126 days; one year is the recommended minimum.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (2itesting.com).

  • Valid certificate (65 days left)

    The certificate from Let's Encrypt · YR2 verifies for 2itesting.com and is valid for another 65 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://2itesting.com redirects to the secure version.

  • HTTP/2

    The server speaks HTTP/2, so browsers load many files over one connection.

  • All 33 links work

    All 33 links checked from your homepage (29 internal, 4 external) answered without errors.

Domain and trust

1 to fix
  • Domain expires in 17 days

    2itesting.com is registered until Nov 2026. If it lapses, the site and its email stop working and someone else can buy the name. Renew it, and turn on auto-renew.

  • No CAA record

    2itesting.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

    2itesting.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 14 years old

    14 years

    2itesting.com was registered in Nov 2011 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.

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 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 852 words of copy

    The homepage carries about 852 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: “Book a discovery session”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Get in touch”, “Book a discovery session” and “Learn more”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 18 testimonial or review blocks, 22 customer or partner logos and 12 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and LinkedIn Insight.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

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

Email authentication

95
  • Email authentication score: 95/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.

3 checks passed
  • DMARC policy: reject

    DMARC tells receivers to reject mail that fails authentication, and sends you reports.

  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:spf.protection.outlook.com include:smtproutes.com include:spf.spotler.co.uk include:spf.cloud.castle-cs.…”.

  • DKIM signing found

    A DKIM key is published (selector “selector1” and “selector2”), so receivers can verify mail really came from you.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 17 other companies contacted

    Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Analytics
Google Tag Manager
Hosting
Node4

Company

Employees
340
Headquarters
Edinburgh

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on 2itesting.com, including 10 speed issues, 5 SEO issues 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