rithvik.me website review

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

8 third-party services load with your homepage (substackcdn.com, Google Tag Manager and substack.com and others), adding 2.5 MB and 1.0 s of main-thread time.

Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.

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

substackcdn.com costs a phone 504 ms of main-thread work and 2.0 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.

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

3 images could be 98 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

Your largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (2.9 s).

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.1 MB in 298 requests on a phone: scripts 2.5 MB (209), stylesheets 331 KiB (50) and images 199 KiB (25). Under 2 MB keeps phones on slow connections fast.

3 images (107 KiB) 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.

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

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

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

Your title is 68 characters, so Google will cut it off around 60: “Rithvik Podduturi | Content Creator & Web Designer | SaaS Enthusiast”.

There are 3 <h1> headlines (“Crafting Engaging Digital Experiences to Transfor…”, “My Services” and “Client Testimonials”). One clear main headline is easier for people and search engines.

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

No XML sitemap at https://rithvik.me/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 28 pages on rithvik.me and 9 external pages.

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.

There is no https://rithvik.me/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.

https://rithvik.me/articles has no meta description, so Google writes the search snippet from whatever text it finds.

https://rithvik.me/contact has 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.

https://rithvik.me/about, https://rithvik.me/articles, https://rithvik.me/portfolio, https://rithvik.me/contact, https://rithvik.me/work-with-me and https://rithvik.me/privacy-and-terms and 1 other took over 3 s to send their HTML from our server.

We fetched 7 pages linked from your homepage and read each the way a search engine does.

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

1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

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

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 695 words of visible text.

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.

Opening the homepage sets 11 cookies, 2 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.