Website review, no card needed

awfis.com logo

awfis.com website review

Visit site (opens in a new tab)Reviewed 31 October 202647 issues · 85 checks

This review found 47 issues worth fixing on awfis.com, 21 of them high impact, across 85 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
6.1 s2.1 sMay 9Oct 245.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.6 s
May 16, 20262.6 s
May 23, 20262.6 s
May 30, 20262.6 s
Jun 6, 20262.6 s
Jun 13, 20262.6 s
Jun 20, 20262.7 s
Jun 27, 20263.1 s
Jul 4, 20263.7 s
Jul 11, 20264.0 s
Jul 18, 20263.9 s
Jul 25, 20263.6 s
Aug 1, 20263.1 s
Aug 8, 20262.9 s
Aug 15, 20262.9 s
Aug 22, 20263.1 s
Aug 29, 20263.6 s
Sep 5, 20264.3 s
Sep 12, 20265.1 s
Sep 19, 20265.6 s
Sep 26, 20265.6 s
Oct 3, 20265.6 s
Oct 10, 20265.6 s
Oct 17, 20265.6 s
Oct 24, 20265.3 s
Real-visitor tap response (INP)75th percentile, phones
302 ms230 msMay 9Oct 24266 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026250 ms
May 16, 2026244 ms
May 23, 2026239 ms
May 30, 2026238 ms
Jun 6, 2026241 ms
Jun 13, 2026243 ms
Jun 20, 2026247 ms
Jun 27, 2026260 ms
Jul 4, 2026281 ms
Jul 11, 2026294 ms
Jul 18, 2026290 ms
Jul 25, 2026279 ms
Aug 1, 2026262 ms
Aug 8, 2026249 ms
Aug 15, 2026250 ms
Aug 22, 2026257 ms
Aug 29, 2026261 ms
Sep 5, 2026266 ms
Sep 12, 2026266 ms
Sep 19, 2026267 ms
Sep 26, 2026267 ms
Oct 3, 2026268 ms
Oct 10, 2026271 ms
Oct 17, 2026271 ms
Oct 24, 2026266 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 awfis.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. awfis.com at 1.4 s1.4 s
  2. awfis.com at 2.8 s2.8 s
  3. awfis.com at 4.3 s4.3 s
  4. awfis.com at 5.7 s5.7 s
  5. awfis.com at 7.1 s7.1 s
  6. awfis.com at 8.5 s8.5 s
  7. awfis.com at 10.0 s10.0 s
  8. awfis.com at 11.4 s11.4 s

Speed

11 to fix44
  • Improve image delivery

    3.6 s · 14.1 MB

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

  • Reduce unused JavaScript

    2.3 s · 564 KiB

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

  • Use efficient cache lifetimes

    1.8 s · 794 KiB

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

  • Render-blocking requests

    2.0 s

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

  • Reduce unused CSS

    1.2 s · 104 KiB

    About 104 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 44

    44/100

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

  • Legacy JavaScript

    350 ms · 30 KiB

    Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

  • Main-thread work: 3.6 s

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

  • 13 long tasks on the main thread

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

  • 1,820 HTML elements

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

  • gokwik.co adds 77 ms

    77 ms

    gokwik.co costs a phone 77 ms of main-thread work and 588 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Clarity and gokwik.co and others), adding 959 KiB and 417 ms of main-thread time.

  • Minify CSS

    150 ms · 20 KiB

    20 KiB could be saved by minifying CSS.

  • Minify JavaScript

    150 ms · 17 KiB

    17 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

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

  • 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: 15 ms

    15 ms

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

Core Web Vitals

12 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: 7.3 s

    7.3 s

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

  • Real-user FCP: 7.6 s

    7.6 s

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

  • Largest Contentful Paint: 73.9 s

    73.9 s

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

  • Speed Index: 26.2 s

    26.2 s

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

  • Time to Interactive: 79.0 s

    79.0 s

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

  • First Contentful Paint: 5.6 s

    5.6 s

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

  • Real-user INP: 255 ms

    255 ms

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

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

    +108%

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Total Blocking Time: 457 ms

    457 ms

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +9%

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

2 checks passed
  • Real-user CLS: 0.01

    0.01

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

  • Cumulative Layout Shift: 0.003

    0.003

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

Images and page weight

3 to fix45
  • Page weight: 23.9 MB in 210 requests

    23.9 MB

    Your homepage downloads 23.9 MB in 210 requests on a phone: images 21.3 MB (79), scripts 1.6 MB (51) and fonts 738 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 15.4 MB together. On a phone connection a single image that size takes seconds.

  • 37 images in older formats

    37 images (19.5 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.

  • About 6.8 g of CO₂ per visit

    6.77 g

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

2 checks passed
  • 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

9 to fixGoogle 7766
  • 7 images without alt text

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

  • Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

    Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (4 elements).

  • Invalid ARIA attributes

    3 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Unlabelled dropdowns

    3 dropdowns have no label.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 35 text elements with low contrast

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

  • 20 form fields without a label

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

  • ARIA input fields do not have accessible names

    ARIA input fields do not have accessible names (4 elements).

  • Headings skip levels

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

1 checks passed
  • 10 automated accessibility rules passed

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

SEO

4 to fixGoogle 7786
  • 52 links crawlers can't follow

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

  • No structured data

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

  • 4 H1 headlines

    There are 4 <h1> headlines (“Elite EnterpriseOffice Spaces”, “India's Largest Integrated Workspace Solutions Pl…” and “Discover Transform by Awfis”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 163 internal links, 7 external

    The homepage links to 163 pages on awfis.com and 7 external pages.

5 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Discover premium coworking spaces in India with flexible plans. Awfis offers shared office space solutions for startups…”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Shared and Coworking Office Spaces for Rent in India | Awfis”.

  • Canonical URL set

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

  • 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.awfis.com/sitemap.xml.

AI search readiness

2 to fix75
  • 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.

  • Some text only appears after JavaScript runs

    37%

    The HTML your server sends has 2,004 of the 5,488 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

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

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

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

3 to fixGoogle 6587
  • 44 distorted images

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

  • 3 third-party cookies

    3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

  • 1 low-resolution image

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

    The homepage carries about 5,488 words of visible text.

4 checks passed
  • 101 calls to action

    The homepage has 101 calls to action, for example “Request a visit”, “Sign up” and “Book a Tour 1860 258 6633”.

  • 4 short forms

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

  • Analytics in place

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

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies, 1 of them by other companies (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.

  • 25 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Analytics | Google Tag Manager
Hosting
AWS

Company

Founded
2015
Headquarters
Delhi

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on awfis.com, including 23 speed issues, 4 SEO issues and 2 conversion gaps. 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