Website review, no card needed
evaly.com.bd website review
Visit site (opens in a new tab)Reviewed 30 October 202612 issues · 76 checks
This review found 12 issues worth fixing on evaly.com.bd, 6 of them high impact, across 76 checks. The most urgent: 466 text elements with low contrast. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
94AClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.5 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.7 s |
| Sep 12, 2026 | 3.9 s |
| Sep 19, 2026 | 4.0 s |
| Sep 26, 2026 | 4.0 s |
| Oct 3, 2026 | 4.1 s |
| Oct 10, 2026 | 3.8 s |
| Oct 17, 2026 | 3.3 s |
| Oct 24, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 262 ms |
| Jun 6, 2026 | 263 ms |
| Jun 13, 2026 | 216 ms |
| Jun 20, 2026 | 207 ms |
| Jun 27, 2026 | 214 ms |
| Jul 4, 2026 | 217 ms |
| Jul 11, 2026 | 220 ms |
| Jul 18, 2026 | 225 ms |
| Jul 25, 2026 | 226 ms |
| Aug 1, 2026 | 227 ms |
| Aug 8, 2026 | 226 ms |
| Aug 15, 2026 | 220 ms |
| Aug 22, 2026 | 218 ms |
| Aug 29, 2026 | 213 ms |
| Sep 5, 2026 | 219 ms |
| Sep 12, 2026 | 219 ms |
| Sep 19, 2026 | 215 ms |
| Sep 26, 2026 | 213 ms |
| Oct 3, 2026 | 206 ms |
| Oct 10, 2026 | 182 ms |
| Oct 17, 2026 | 159 ms |
| Oct 24, 2026 | 158 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
Speed
Render-blocking requests
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need.
1 third-party service on the page
1 third-party service load with your homepage (Cloudflare), adding 10 KiB and 9 ms of main-thread time.
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.
Use efficient cache lifetimes
4 KiB1 file is served with short cache lifetimes, so returning visitors download them again (4 KiB).
3 checks passed
Mobile performance score: 100
100/100Your mobile performance score is 100. That is in Google's “good” band (90 and up).
Main-thread work: 0.1 s
A phone's processor spends 0.1 s on main-thread work while loading, 27 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
14 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 177 ms
177 msReal visitors wait 177 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 727 ms
727 msReal visitors wait 727 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 40% faster for real visitors
-40%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 262 ms to 158 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.6 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
First Contentful Paint: 0.8 s
0.8 sThe first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 0.8 s
0.8 sYour largest element renders in 0.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “This website is using a security service to protect itself …”.
Speed Index: 0.8 s
0.8 sVisually, the page fills in at 0.8 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Time to Interactive: 0.8 s
0.8 sThe page is fully interactive after 0.8 s.
Images and page weight
2 images far larger than shown
128 KiB2 images are downloaded at several times the size a phone draws them, for example 66369dcf8d788e9a0c84b51302b74941.png at 600 px wide, shown at 72 px. Resized copies would save about 128 KiB.
10 images below the first screen load straight away
10 images further down the page (405 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
7 images in older formats
7 images (327 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.
About 0.01 g of CO₂ per visit
0.01 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.01 g of CO₂e: 0.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 24 KiB in 6 requests
24 KiBYour homepage downloads 24 KiB in 6 requests on a phone: scripts 10 KiB (1), stylesheets 5 KiB (1) and images 5 KiB (2). That is a lean page.
Accessibility
466 text elements with low contrast
466 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (1,013 elements)
All page content should be contained by landmarks: 1,013 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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3, h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 96 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Blocked from indexing
Google's crawler is blocked from indexing this page.
Error status code
The page answers with an error status, so search engines may drop it.
179 internal links, 2 external
The homepage links to 179 pages on evaly.com.bd and 2 external pages.
8 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Shop electronics, fashion, groceries, home appliances & beauty online in Bangladesh on Evaly. Enjoy Cash on Delivery & …”.
One H1 headline
Your main headline reads: “Online Shopping in Bangladesh, All in One Place”.
Title: 56 characters
Your title is a healthy 56 characters: “Evaly — Online Shopping in Bangladesh | Cash on Delivery”.
Canonical URL set
The canonical URL is https://evaly.com.bd/.
Structured data in place
Structured data found: FAQPage, MobileApplication, Organization and WebSite.
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://evaly.com.bd/sitemap.xml.
AI search readiness
4 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,972 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://evaly.com.bd/llms.txt (3 KiB, 21 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://evaly.com.bd/track declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
1 page with very little text
https://evaly.com.bd/track 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 132 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
222 of 224 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
About 3,429 words of copy
The homepage carries about 3,429 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop now”.
5 calls to action
The homepage has 5 calls to action, for example “Track order”, “Shop now” and “Track your order”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, a star rating and 2 trust badges.
Analytics in place
Analytics detected: Google Analytics and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 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
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
3 other companies contacted
Loading the homepage contacts 3 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 evaly.com.bd, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Analytics
- Hosting
- Cloudflare
Company
- Founded
- 2018
- Headquarters
- Dhaka
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 12 issues on evaly.com.bd, including 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.