Website review, no card needed

grynow.in logo

grynow.in website review

Visit site (opens in a new tab)Reviewed 19 October 202635 issues · 86 checks

This review found 35 issues worth fixing on grynow.in, 12 of them high impact, across 86 checks. The most urgent: page weight: 68.3 MB in 124 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.9 s1.6 sMay 2Oct 171.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.6 s
May 9, 20261.6 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.7 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
148 ms123 msMay 2Oct 17145 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026130 ms
May 9, 2026129 ms
May 16, 2026128 ms
May 23, 2026133 ms
May 30, 2026133 ms
Jun 6, 2026136 ms
Jun 13, 2026141 ms
Jun 20, 2026138 ms
Jun 27, 2026135 ms
Jul 4, 2026134 ms
Jul 11, 2026138 ms
Jul 18, 2026138 ms
Jul 25, 2026139 ms
Aug 1, 2026137 ms
Aug 8, 2026130 ms
Aug 15, 2026131 ms
Aug 22, 2026135 ms
Aug 29, 2026135 ms
Sep 5, 2026135 ms
Sep 12, 2026130 ms
Sep 19, 2026126 ms
Sep 26, 2026128 ms
Oct 3, 2026130 ms
Oct 10, 2026139 ms
Oct 17, 2026145 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 grynow.in (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. grynow.in at 0.5 s0.5 s
  2. grynow.in at 1.0 s1.0 s
  3. grynow.in at 1.5 s1.5 s
  4. grynow.in at 2.0 s2.0 s
  5. grynow.in at 2.5 s2.5 s
  6. grynow.in at 3.0 s3.0 s
  7. grynow.in at 3.5 s3.5 s
  8. grynow.in at 4.0 s4.0 s

Speed

8 to fix66
  • Main-thread work: 8.2 s

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

  • Improve image delivery

    15.8 MB

    35 images could be 15.8 MB 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 CDN, Google Tag Manager and Facebook and others), adding 2.2 MB and 1.5 s of main-thread time.

  • Mobile performance score: 66

    66/100

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

  • Reduce unused JavaScript

    954 KiB

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

  • Google CDN adds 689 ms

    689 ms

    Google CDN costs a phone 689 ms of main-thread work and 1.1 MB 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.

  • Google Tag Manager adds 448 ms

    448 ms

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

  • 1,631 HTML elements

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

  • 19 long tasks on the main thread

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

  • Use efficient cache lifetimes

    193 KiB

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

  • Reduce unused CSS

    21 KiB

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

  • Legacy JavaScript

    12 KiB

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

  • Minify CSS

    7 KiB

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

1 checks passed
  • Server response: 209 ms

    209 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • Time to Interactive: 67.7 s

    67.7 s

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

  • Speed Index: 12.2 s

    12.2 s

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

  • Total Blocking Time: 651 ms

    651 ms

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

  • Real-user TTFB: 910 ms

    910 ms

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Largest Contentful Paint: 2.9 s

    2.9 s

    Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Grynow is the best influencer marketing agency in India, he…”. Most of its time is element render delay (1.2 s).

  • 13 images without width and height

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

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

    +10%

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

  • Largest content (LCP) held steady for real visitors

    +8%

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

5 checks passed
  • Real-user LCP: 1.2 s

    1.2 s

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

  • Real-user INP: 173 ms

    173 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

5 to fix18
  • Page weight: 68.3 MB in 124 requests

    68.3 MB

    Your homepage downloads 68.3 MB in 124 requests on a phone: media 37.0 MB (8), images 28.6 MB (81) and scripts 1.9 MB (16). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 3.2 MB together. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    3.7 MB

    4 images are downloaded at several times the size a phone draws them, for example raise-beauty.png at 1,645 px wide, shown at 59 px. Resized copies would save about 3.7 MB.

  • 4 images in older formats

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

  • 4 images below the first screen load straight away

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

  • About 19.4 g of CO₂ per visit

    19.36 g

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

Accessibility

7 to fixGoogle 8790
  • 16 tap targets too small

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

  • 7 text elements with low contrast

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • 6 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 150 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

3 to fixGoogle 10088
  • Meta description is long (196 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: missing name”.

  • 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 X (Twitter) card tag

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

  • 141 internal links, 10 external

    The homepage links to 141 pages on grynow.in and 10 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Best Influencer Marketing Agency in India”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “Best Influencer Marketing Agency in India”.

  • Canonical URL set

    The canonical URL is https://www.grynow.in/.

  • 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.grynow.in/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.grynow.in/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: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

100
  • 2 pages with very little text

    https://www.grynow.in/influencer-marketing-case-studies-in-middle-east.html and https://www.grynow.in/ugc-campaigns-in-india.html 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 83 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

3 to fixGoogle 9285
  • 2 small tap targets

    2 of 9 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 “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • About 2,031 words of copy

    The homepage carries about 2,031 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: “Contact Us”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact Us”, “Talk to Influencer Marketing experts” and “contact us”.

  • 1 short form

    A short form (5 fields at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 43 testimonial or review blocks, 8 customer or partner logos and 5 trust badges.

  • Analytics in place

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

  • Direct contact links

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

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.

  • 4 cookies set on arrival

    4

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 grynow.in, 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 35 issues on grynow.in, including 16 speed issues and 3 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