Website review, no card needed

aptinverex.com logo

aptinverex.com website review

Visit site (opens in a new tab)Reviewed 24 October 202652 issues · 91 checks

This review found 52 issues worth fixing on aptinverex.com, 18 of them high impact, across 91 checks. The most urgent: improve image delivery. 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
5.3 s2.1 sMay 2Oct 174.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.4 s
May 9, 20262.6 s
May 16, 20263.0 s
May 23, 20263.4 s
May 30, 20264.2 s
Jun 6, 20264.3 s
Jun 13, 20264.3 s
Jun 20, 20264.3 s
Jun 27, 20264.4 s
Jul 4, 20264.5 s
Jul 11, 20264.6 s
Jul 18, 20264.5 s
Jul 25, 20264.5 s
Aug 1, 20264.5 s
Aug 8, 20264.5 s
Aug 15, 20264.6 s
Aug 22, 20264.4 s
Aug 29, 20264.3 s
Sep 5, 20264.4 s
Sep 12, 20264.4 s
Sep 19, 20264.7 s
Sep 26, 20264.8 s
Oct 3, 20264.8 s
Oct 10, 20264.9 s
Oct 17, 20264.9 s
Real-visitor tap response (INP)75th percentile, phones
170 ms85 msMay 2Oct 17106 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202695 ms
May 9, 202695 ms
May 16, 202697 ms
May 23, 202697 ms
May 30, 202699 ms
Jun 6, 2026101 ms
Jun 13, 2026101 ms
Jun 20, 2026102 ms
Jun 27, 2026104 ms
Jul 4, 2026105 ms
Jul 11, 2026107 ms
Jul 18, 2026109 ms
Jul 25, 2026110 ms
Aug 1, 2026109 ms
Aug 8, 2026107 ms
Aug 15, 2026106 ms
Aug 22, 2026123 ms
Aug 29, 2026157 ms
Sep 5, 2026159 ms
Sep 12, 2026160 ms
Sep 19, 2026147 ms
Sep 26, 2026106 ms
Oct 3, 2026106 ms
Oct 10, 2026106 ms
Oct 17, 2026106 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 aptinverex.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aptinverex.com at 0.6 s0.6 s
  2. aptinverex.com at 1.2 s1.2 s
  3. aptinverex.com at 1.8 s1.8 s
  4. aptinverex.com at 2.4 s2.4 s
  5. aptinverex.com at 3.0 s3.0 s
  6. aptinverex.com at 3.6 s3.6 s
  7. aptinverex.com at 4.2 s4.2 s
  8. aptinverex.com at 4.7 s4.7 s

Speed

12 to fix25
  • Improve image delivery

    2.0 s · 3.2 MB

    24 images could be 3.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.

  • Render-blocking requests

    3.3 s

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

  • Use efficient cache lifetimes

    1.6 s · 1.2 MB

    66 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

  • Mobile performance score: 25

    25/100

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

  • Reduce unused JavaScript

    900 ms · 524 KiB

    About 524 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Reduce unused CSS

    900 ms · 474 KiB

    About 474 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.

  • Reduce initial server response time

    902 ms

    Reduce initial server response time. Google estimates savings of 902 ms on a phone.

  • Document request latency

    900 ms

    The HTML itself could arrive about 900 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • 6 third-party services on the page

    6 third-party services load with your homepage (botsify.com, Google Tag Manager and Google/Doubleclick Ads and others), adding 1.3 MB and 336 ms of main-thread time.

  • botsify.com adds 182 ms

    182 ms

    botsify.com costs a phone 182 ms of main-thread work and 964 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: 2.2 s

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

  • Server response: 1.0 s

    1.0 s

    Your server takes 1.0 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 8 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Legacy JavaScript

    19 KiB

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

  • Minify CSS

    17 KiB

    17 KiB could be saved by minifying CSS.

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

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 LCP: 8.5 s

    8.5 s

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

  • Real-user CLS: 1.00

    1.00

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

  • Real-user FCP: 3.8 s

    3.8 s

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

  • Largest Contentful Paint: 26.0 s

    26.0 s

    Your largest element takes 26.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.9 s

    26.9 s

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

  • Cumulative Layout Shift: 1.033

    1.033

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

  • Speed Index: 8.1 s

    8.1 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

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

    +94%

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • 86 images without width and height

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

  • Total Blocking Time: 410 ms

    410 ms

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

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

    +12%

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

1 checks passed
  • Real-user INP: 124 ms

    124 ms

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

Images and page weight

5 to fix28
  • Page weight: 8.1 MB in 88 requests

    8.1 MB

    Your homepage downloads 8.1 MB in 88 requests on a phone: images 5.3 MB (40), fonts 1.2 MB (9) and scripts 1.0 MB (20). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    about_8_1.png weighs 587 KiB. On a phone connection a single image that size takes seconds.

  • 22 images in older formats

    22 images (3.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.

  • 23 images below the first screen load straight away

    23 images further down the page (3.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 2 images far larger than shown

    36 KiB

    2 images are downloaded at several times the size a phone draws them, for example Inverex-New-Logo.png at 1,200 px wide, shown at 267 px. Resized copies would save about 36 KiB.

  • About 2.3 g of CO₂ per visit

    2.29 g

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

Accessibility

7 to fixGoogle 8490
  • 3 buttons without a name

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

  • 11 text elements with low contrast

    11 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 (28 elements)

    All page content should be contained by landmarks: 28 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.

  • 9 form fields without a label

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

  • 4 links without text

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

  • Page language is “zxx”

    The page declares lang=“zxx”, which is not a usable language code (“zxx” means “no linguistic content”), so screen readers and translation tools guess.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 44 images in the HTML carry an alt attribute.

  • 36 automated accessibility rules passed

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

SEO

7 to fixGoogle 9274
  • No structured data

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

  • Meta description is short (58 characters)

    Your meta description is only 58 characters: “Inverex - Construction & Real Estate Company HTML Template”. 70 to 160 characters is enough to sell the click.

  • 6 H1 headlines

    There are 6 <h1> headlines (“Pakistan’s Leading”, “Solar Brand!” and “Elevating Green Energy with”). One clear main headline is easier for people and search engines.

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

  • 3 links crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 85 internal links, 105 external

    The homepage links to 85 pages on aptinverex.com and 105 external pages.

2 checks passed
  • Title: 50 characters

    Your title is a healthy 50 characters: “Inverex Solar Energy | Pakistan's No:1 Solar Brand”.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

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://aptinverex.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.

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 (984 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix67
  • 1 linked page is broken

    Your homepage links to https://aptinverex.com/project-details, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 15 pages share a title

    /, https://aptinverex.com/about, https://aptinverex.com/solar-inverters, https://aptinverex.com/solar-panels, https://aptinverex.com/solar-batteries and https://aptinverex.com/dealers and 9 others all use the title “Inverex Solar Energy | Pakistan's No:1 Solar Brand”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages share a meta description

    https://aptinverex.com/about, https://aptinverex.com/solar-inverters, https://aptinverex.com/solar-panels, https://aptinverex.com/solar-batteries, https://aptinverex.com/dealers and https://aptinverex.com/events and 8 others use the same meta description. A description written for each page earns more clicks.

  • 3 pages with very little text

    https://aptinverex.com/print, https://aptinverex.com/tv-commercials and https://aptinverex.com/certificates have 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 18 found) and read each the way a search engine does.

5 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9291
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Cannot set properties of undefined (setting 'cssText')”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    19 of 20 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • Thin social proof

    Social proof on the homepage: 7 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 1,014 words of copy

    The homepage carries about 1,014 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: “CONTACT US NOW”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “GET A QUOTE”, “Contact Us Now” and “CONTACT SALES”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

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

  • 9 other companies contacted

    Loading the homepage contacts 9 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 aptinverex.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 Tag Manager

Company

Employees
220
Headquarters
Karachi

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on aptinverex.com, including 25 speed issues, 7 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