devagabond.com website review

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

13 images could be 520 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

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

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

8 third-party services load with your homepage (Shopify, POWr and automizely.com and others), adding 1.1 MB and 544 ms of main-thread time.

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

Shopify costs a phone 311 ms of main-thread work and 947 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.

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

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

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

33 KiB could be saved by minifying JavaScript.

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

9 KiB could be saved by minifying CSS.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

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

The layout shifts by 0.219 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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.5 MB in 332 requests on a phone: scripts 1.2 MB (189), images 959 KiB (20) and other files 834 KiB (92). Under 2 MB keeps phones on slow connections fast.

Diwali_sale_12f91ee1-a99b-448c-a8ed-b5f60e4f348b_800x.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

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

2 elements hidden from screen readers can still receive keyboard focus.

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

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

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

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

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

Your title is only 10 characters: “Devagabond”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

The homepage links to 65 pages on devagabond.com and 4 external pages.

The HTML your server sends has 629 of the 1,311 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

/collections/loot-sale, /collections/all, /collections/gym-bags, /collections/school-bags0-under-499, /pages/bulkrder and /pages/contact have no meta description, so Google writes the search snippet from whatever text it finds.

/products/school-bag-9 and /products/school-bag-6 use the same meta description. A description written for each page earns more clicks.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

3 links go through two or more redirects, for example https://devagabond.com/account.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

devagabond.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

devagabond.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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 1,311 words of visible text.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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 10 cookies (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 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.