Website review, no card needed

akshayapatra.org logo

akshayapatra.org website review

Visit site (opens in a new tab)Reviewed 19 November 202648 issues · 85 checks

This review found 48 issues worth fixing on akshayapatra.org, 20 of them high impact, across 85 checks. The most urgent: reduce unused JavaScript. 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.4 s2.2 sMay 30Nov 143.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.4 s
Jun 6, 20262.6 s
Jun 13, 20262.9 s
Jun 20, 20263.1 s
Jun 27, 20263.3 s
Jul 4, 20263.2 s
Jul 11, 20263.1 s
Jul 18, 20262.9 s
Jul 25, 20262.7 s
Aug 1, 20262.7 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.8 s
Aug 29, 20262.7 s
Sep 5, 20262.7 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.8 s
Oct 3, 20262.9 s
Oct 10, 20263.0 s
Oct 17, 20263.0 s
Oct 24, 20263.0 s
Oct 31, 20263.1 s
Nov 7, 20263.2 s
Nov 14, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
494 ms154 msMay 30Nov 14402 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026193 ms
Jun 6, 2026212 ms
Jun 13, 2026239 ms
Jun 20, 2026274 ms
Jun 27, 2026283 ms
Jul 4, 2026301 ms
Jul 11, 2026292 ms
Jul 18, 2026287 ms
Jul 25, 2026313 ms
Aug 1, 2026412 ms
Aug 8, 2026439 ms
Aug 15, 2026449 ms
Aug 22, 2026455 ms
Aug 29, 2026397 ms
Sep 5, 2026371 ms
Sep 12, 2026371 ms
Sep 19, 2026371 ms
Sep 26, 2026373 ms
Oct 3, 2026379 ms
Oct 10, 2026405 ms
Oct 17, 2026402 ms
Oct 24, 2026406 ms
Oct 31, 2026410 ms
Nov 7, 2026384 ms
Nov 14, 2026402 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 akshayapatra.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. akshayapatra.org at 1.2 s1.2 s
  2. akshayapatra.org at 2.3 s2.3 s
  3. akshayapatra.org at 3.5 s3.5 s
  4. akshayapatra.org at 4.6 s4.6 s
  5. akshayapatra.org at 5.8 s5.8 s
  6. akshayapatra.org at 6.9 s6.9 s
  7. akshayapatra.org at 8.1 s8.1 s
  8. akshayapatra.org at 9.3 s9.3 s

Speed

11 to fix45
  • Reduce unused JavaScript

    3.9 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.9 s faster on a phone.

  • Improve image delivery

    1.6 s · 2.2 MB

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

  • Render-blocking requests

    1.3 s

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

  • Mobile performance score: 45

    45/100

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

  • Main-thread work: 4.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (reddit, Google Tag Manager and Facebook and others), adding 856 KiB and 1.1 s of main-thread time.

  • Use efficient cache lifetimes

    350 ms · 371 KiB

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

  • Reduce unused CSS

    450 ms · 87 KiB

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

  • 20 long tasks on the main thread

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

  • reddit adds 394 ms

    394 ms

    reddit costs a phone 394 ms of main-thread work and 40 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.

  • Google Tag Manager adds 213 ms

    213 ms

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

  • Legacy JavaScript

    200 ms · 46 KiB

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

  • Font display

    100 ms

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

  • Minify CSS

    9 KiB

    9 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: 4 ms

    4 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 30.2 s

    30.2 s

    Your largest element takes 30.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Special occasion”.

  • Time to Interactive: 35.6 s

    35.6 s

    The page becomes fully interactive after 35.6 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: 763 ms

    763 ms

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Real-user INP: 205 ms

    205 ms

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

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

    +94%

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

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

    +30%

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

  • 46 images without width and height

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

4 checks passed
  • 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.7 s

    1.7 s

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

  • Real-user TTFB: 793 ms

    793 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix43
  • Page weight: 7.5 MB in 212 requests

    7.5 MB

    Your homepage downloads 7.5 MB in 212 requests on a phone: images 4.4 MB (60), scripts 2.5 MB (59) and fonts 341 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 26 images in older formats

    26 images (2.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.

  • 24 images below the first screen load straight away

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

  • 4 images far larger than shown

    273 KiB

    4 images are downloaded at several times the size a phone draws them, for example Shayan.jpg at 1,218 px wide, shown at 260 px. Resized copies would save about 273 KiB.

  • About 2.1 g of CO₂ per visit

    2.13 g

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

Accessibility

11 to fixGoogle 7684
  • 16 text elements with low contrast

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

  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 5 images without alt text

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

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

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

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

  • 10 links without text

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

  • 9 form fields without a label

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

  • Headings skip levels

    Headings skip levels (h2 → h5, h2 → h5 and h2 → h4), 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 11 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 7771
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Akshaya Patra-NGO in India Supporting Food & Education of Children”.

  • 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 long (163 characters)

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

  • 6 links crawlers can't follow

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 143 internal links, 6 external

    The homepage links to 143 pages on akshayapatra.org and 6 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.akshayapatra.org/.

  • 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.akshayapatra.org/sitemap.xml.

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.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.akshayapatra.org/llms.txt (6 KiB, 31 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 99 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

2 to fixGoogle 9278
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=25150305&tm=gtm002&Ver=2&mid=7ea619dd-e90b-45a8-bd8c-b26c3776c4ac&bo=1&sid=84c78b90e43411f19db7819028d322ea&vid=84c78d00e43411f1ba56579acbc76a57&vids=1&msclkid=N&gtm_t.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Uncaught ReferenceError: feedify_options is not defined”.

  • 1 low-resolution image

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    20 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 fix83
  • 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 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,220 words of copy

    The homepage carries about 1,220 words of visible text.

5 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us”, “Register Here” and “Sign up”.

  • 4 short forms

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

  • Social proof on the page

    Social proof on the homepage: 5 testimonial or review blocks and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 10 trackers load before any consent

    10

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

  • 21 cookies set on arrival

    21

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

  • 44 other companies contacted

    Loading the homepage contacts 44 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 akshayapatra.org, 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
Hosting
Cloudflare

Company

Employees
8,627
Founded
2000
Headquarters
Bengaluru

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on akshayapatra.org, including 22 speed issues, 6 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