Website review, no card needed

aiswindows.com logo

aiswindows.com website review

Visit site (opens in a new tab)Reviewed 18 October 202643 issues · 87 checks

This review found 43 issues worth fixing on aiswindows.com, 13 of them high impact, across 87 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
4.0 s2.9 sApr 25Oct 103.7 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20263.0 s
May 2, 20263.1 s
May 9, 20263.0 s
May 16, 20263.1 s
May 23, 20263.3 s
May 30, 20263.4 s
Jun 6, 20263.5 s
Jun 13, 20263.6 s
Jun 20, 20263.6 s
Jun 27, 20263.7 s
Jul 4, 20263.7 s
Jul 11, 20263.8 s
Jul 18, 20263.9 s
Jul 25, 20263.9 s
Aug 1, 20263.9 s
Aug 8, 20263.8 s
Aug 15, 20263.8 s
Aug 22, 20263.8 s
Aug 29, 20263.8 s
Sep 5, 20263.8 s
Sep 12, 20263.8 s
Sep 19, 20263.7 s
Sep 26, 20263.7 s
Oct 3, 20263.7 s
Oct 10, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
294 ms165 msApr 25Oct 10279 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026182 ms
May 2, 2026184 ms
May 9, 2026180 ms
May 16, 2026186 ms
May 23, 2026201 ms
May 30, 2026238 ms
Jun 6, 2026261 ms
Jun 13, 2026272 ms
Jun 20, 2026274 ms
Jun 27, 2026272 ms
Jul 4, 2026271 ms
Jul 11, 2026271 ms
Jul 18, 2026274 ms
Jul 25, 2026269 ms
Aug 1, 2026260 ms
Aug 8, 2026254 ms
Aug 15, 2026253 ms
Aug 22, 2026249 ms
Aug 29, 2026246 ms
Sep 5, 2026245 ms
Sep 12, 2026246 ms
Sep 19, 2026250 ms
Sep 26, 2026260 ms
Oct 3, 2026271 ms
Oct 10, 2026279 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 aiswindows.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aiswindows.com at 0.7 s0.7 s
  2. aiswindows.com at 1.5 s1.5 s
  3. aiswindows.com at 2.2 s2.2 s
  4. aiswindows.com at 2.9 s2.9 s
  5. aiswindows.com at 3.7 s3.7 s
  6. aiswindows.com at 4.4 s4.4 s
  7. aiswindows.com at 5.1 s5.1 s
  8. aiswindows.com at 5.9 s5.9 s

Speed

9 to fix58
  • Render-blocking requests

    1.6 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.6 s.

  • Reduce unused JavaScript

    1.2 s · 272 KiB

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

  • Mobile performance score: 58

    58/100

    Your mobile performance score is 58 (desktop: 77). Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and JSDelivr CDN and others), adding 824 KiB and 743 ms of main-thread time.

  • Use efficient cache lifetimes

    600 ms · 180 KiB

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

  • Google Tag Manager adds 495 ms

    495 ms

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

  • Reduce unused CSS

    300 ms · 53 KiB

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

  • 2,828 HTML elements

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

  • Main-thread work: 2.3 s

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

  • 8 long tasks on the main thread

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

  • Improve image delivery

    150 ms · 86 KiB

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

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 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.

1 checks passed
  • Server response: 54 ms

    54 ms

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

Core Web Vitals

13 to fix33
  • Fails Core Web Vitals for real visitors

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

  • Real-user FCP: 3.7 s

    3.7 s

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

  • Real-user TTFB: 2.1 s

    2.1 s

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

  • Largest Contentful Paint: 7.7 s

    7.7 s

    Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Windows”.

  • Time to Interactive: 9.5 s

    9.5 s

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

  • Real-user LCP: 4.0 s

    4.0 s

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

  • Real-user INP: 324 ms

    324 ms

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

  • Tap response (INP) got 50% slower for real visitors

    +50%

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

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

    +21%

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

  • Speed Index: 5.4 s

    5.4 s

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

  • Total Blocking Time: 436 ms

    436 ms

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 8 images without width and height

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

2 checks passed
  • Real-user CLS: 0.02

    0.02

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

  • Cumulative Layout Shift: 0.007

    0.007

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

Images and page weight

100
  • 1 image in older formats

    1 image (50 KiB) is 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.6 g of CO₂ per visit

    0.56 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.56 g of CO₂e: 67.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: 2.0 MB in 93 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 93 requests on a phone: images 1,021 KiB (65), scripts 867 KiB (13) and stylesheets 67 KiB (2). 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

10 to fixGoogle 7984
  • 20 tap targets too small

    20 tap targets are too small or too close together to hit reliably with a finger.

  • Interactive controls must not be nested (7 elements)

    Interactive controls must not be nested: 7 elements on the page fail this check, rated serious by axe-core.

  • 4 text elements with low contrast

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

  • Links look like plain text

    2 links inside paragraphs rely on colour alone to stand out.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 24 images without alt text

    24 images have no alt text, which hurts accessibility and image search.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 80 links without text

    80 visible links have no text or label, so screen readers cannot say where they go.

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 40 automated accessibility rules passed

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

SEO

4 to fixGoogle 7784
  • Title is long (110 characters)

    Your title is 110 characters, so Google will cut it off around 60: “Aluminium & uPVC Windows and Doors Company | Window & Glass Manufacturers and Suppliers i…”.

  • Meta description is long (246 characters)

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

  • 3 links with vague text

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

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 382 internal links, 16 external

    The homepage links to 382 pages on aiswindows.com and 16 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “AIS Windows”.

  • Canonical URL set

    The canonical URL is https://www.aiswindows.com/.

  • Structured data in place

    Structured data found: Organization and SiteNavigationElement.

  • 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://www.aiswindows.com/sitemap.xml.

AI search readiness

100
4 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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.aiswindows.com/llms.txt (12 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://www.aiswindows.com/exp_center is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://www.aiswindows.com/exp_center has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.aiswindows.com/partner-with-us, https://www.aiswindows.com/customer-testimonials and https://www.aiswindows.com/blog 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 119 found) and read each the way a search engine does.

4 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 a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9285
  • 13 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “$ is not defined”.

  • 21 distorted images

    21 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • About 899 words of copy

    The homepage carries about 899 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Download Brochure” and “Where to Buy”.

  • 18 calls to action

    The homepage has 18 calls to action, for example “Where to Buy”, “Download Brochure” and “Learn More”.

  • Social proof on the page

    Social proof on the homepage: 20 testimonial or review blocks and 5 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

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

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 Meta Pixel (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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 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 aiswindows.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
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 43 issues on aiswindows.com, including 22 speed issues and 4 SEO issues. 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