Website review, no card needed

iqlance.com logo

iqlance.com website review

Visit site (opens in a new tab)Reviewed 3 November 202620 issues · 76 checks

This review found 20 issues worth fixing on iqlance.com, 4 of them high impact, across 76 checks. The most urgent: fails Core Web Vitals for real visitors. 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
3.2 s2.2 sMay 16Oct 313.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.4 s
May 23, 20262.8 s
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.8 s
Jun 20, 20262.7 s
Jun 27, 20263.0 s
Jul 4, 20263.0 s
Jul 11, 20262.9 s
Jul 18, 20263.1 s
Jul 25, 20262.9 s
Aug 1, 20263.1 s
Aug 8, 20262.8 s
Aug 15, 20262.7 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.5 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.5 s
Oct 10, 20262.3 s
Oct 17, 20262.4 s
Oct 24, 20262.7 s
Oct 31, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
190 ms109 msMay 16Oct 31174 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026130 ms
May 23, 2026165 ms
May 30, 2026174 ms
Jun 6, 2026157 ms
Jun 13, 2026168 ms
Jun 20, 2026159 ms
Jun 27, 2026165 ms
Jul 4, 2026179 ms
Jul 11, 2026172 ms
Jul 18, 2026181 ms
Jul 25, 2026180 ms
Aug 1, 2026180 ms
Aug 8, 2026169 ms
Aug 15, 2026148 ms
Aug 22, 2026127 ms
Aug 29, 2026122 ms
Sep 5, 2026120 ms
Sep 12, 2026118 ms
Sep 19, 2026125 ms
Sep 26, 2026125 ms
Oct 3, 2026138 ms
Oct 10, 2026144 ms
Oct 17, 2026148 ms
Oct 24, 2026161 ms
Oct 31, 2026174 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 iqlance.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

1 to fix99
  • 2,623 HTML elements

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

  • Improve image delivery

    70 KiB

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

  • Reduce unused CSS

    70 KiB

    About 70 KiB of CSS is downloaded but never applied on this page.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 65 ms. During a long task the page ignores taps.

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

3 checks passed
  • Mobile performance score: 99

    99/100

    Your mobile performance score is 99. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.8 s

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

  • Server response: 97 ms

    97 ms

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

Core Web Vitals

6 to fix67
  • 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 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.

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Time to Interactive: 3.9 s

    3.9 s

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

  • 7 images without width and height

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

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

    +14%

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

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

    +10%

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

7 checks passed
  • Real-user INP: 174 ms

    174 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Speed Index: 2.6 s

    2.6 s

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

  • Largest Contentful Paint: 1.7 s

    1.7 s

    Your largest element renders in 1.7 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Leading Mobile App and Software Development Company”.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 8 ms

    8 ms

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

Images and page weight

2 to fix83
  • 7 images below the first screen load straight away

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

  • 1 image far larger than shown

    25 KiB

    1 image is downloaded at several times the size a phone draws it, for example iqlance-leptop.png at 800 px wide, shown at 198 px. Resized copies would save about 25 KiB.

  • About 0.4 g of CO₂ per visit

    0.44 g

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

    1.5 MB

    Your homepage downloads 1.5 MB in 211 requests on a phone: images 1.2 MB (178), HTML 189 KiB (1) and fonts 165 KiB (12). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

6 to fixGoogle 9392
  • 2 text elements with low contrast

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

  • 89 images without alt text

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

  • All page content should be contained by landmarks (78 elements)

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

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

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

  • 13 form fields without a label

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

  • Headings skip levels

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

1 checks passed
  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 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

2 to fixGoogle 9293
  • Meta description is long (168 characters)

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

  • 2 links crawlers can't follow

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

  • 280 internal links, 17 external

    The homepage links to 280 pages on iqlance.com and 17 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Leading Mobile App and Software Development Company”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Software & Mobile App Development Company USA | iQlance”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, LocalBusiness, Organization and WebPage.

  • 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.iqlance.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.iqlance.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.

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

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

  • Text is in the HTML

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

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 113 found) and read each the way a search engine does.

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

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9291
  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “X-Frame-Options may only be set via an HTTP header sent along with a document. It may not be set inside <meta>.”.

  • 6 distorted images

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

2 checks passed
  • Tap targets are thumb-sized

    13 of 15 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
  • A 8-field form

    Your longest form asks for 8 fields (5 required). Every extra field lowers completion.

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

    The homepage carries about 2,139 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: “Enquire Now” and “Request a Call Back”.

  • 14 calls to action

    The homepage has 14 calls to action, for example “Enquire Now”, “Contact” and “Request a Quote”.

  • Social proof on the page

    Social proof on the homepage: 5 testimonial or review blocks, 28 customer or partner logos, 4 trust badges and “200 + Happy Clients”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 13 phone links and 7 email links.

  • Phone number on the homepage

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 iqlance.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on iqlance.com, including 7 speed issues, 2 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