Website review, no card needed
eshikhon.com.bd website review
Visit site (opens in a new tab)Reviewed 1 November 202654 issues · 91 checks
This review found 54 issues worth fixing on eshikhon.com.bd, 17 of them high impact, across 91 checks. The most urgent: youTube adds 4.2 s. 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
65D- #111,357 of 120,061 reviewed websitesbeats 6%
- #65,614 of 68,029 online storesbeats 3%
- #2,532 of 2,770 WooCommerce storesbeats 7%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.7 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 175 ms |
| May 16, 2026 | 175 ms |
| May 23, 2026 | 182 ms |
| May 30, 2026 | 191 ms |
| Jun 6, 2026 | 197 ms |
| Jun 13, 2026 | 203 ms |
| Jun 20, 2026 | 205 ms |
| Jun 27, 2026 | 207 ms |
| Jul 4, 2026 | 206 ms |
| Jul 11, 2026 | 201 ms |
| Jul 18, 2026 | 197 ms |
| Jul 25, 2026 | 197 ms |
| Aug 1, 2026 | 196 ms |
| Aug 8, 2026 | 199 ms |
| Aug 15, 2026 | 190 ms |
| Aug 22, 2026 | 187 ms |
| Aug 29, 2026 | 183 ms |
| Sep 5, 2026 | 179 ms |
| Sep 12, 2026 | 186 ms |
| Sep 19, 2026 | 184 ms |
| Sep 26, 2026 | 190 ms |
| Oct 3, 2026 | 205 ms |
| Oct 10, 2026 | 210 ms |
| Oct 17, 2026 | 219 ms |
| Oct 24, 2026 | 223 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
How it loaded on a phone
1.7 s
3.4 s
5.0 s
6.7 s
8.4 s
10.1 s
11.8 s
13.5 s
Speed
YouTube adds 4.2 s
4.2 sYouTube costs a phone 4.2 s of main-thread work and 15.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
1.8 s25 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Main-thread work: 11.3 s
A phone's processor spends 11.3 s on main-thread work while loading, 6.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
8.4 MBAbout 8.4 MB of JavaScript is downloaded but never used on this page.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Facebook and Other Google APIs/SDKs and others), adding 16.8 MB and 4.5 s of main-thread time.
Improve image delivery
950 ms · 1.2 MB11 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Font display
700 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 700 ms).
Use efficient cache lifetimes
411 KiB27 files are served with short cache lifetimes, so returning visitors download them again (411 KiB).
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 352 ms. During a long task the page ignores taps.
1,502 HTML elements
The page has 1,502 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Other Google APIs/SDKs adds 104 ms
104 msOther Google APIs/SDKs costs a phone 104 ms of main-thread work and 400 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 Fonts adds 0 ms
0 msGoogle Fonts costs a phone 0 ms of main-thread work and 556 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.
Reduce unused CSS
150 ms · 105 KiBAbout 105 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.
Legacy JavaScript
30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need.
Minify CSS
6 KiB6 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: 220 ms
220 msYour server sent the HTML in 220 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Speed Index: 38.0 s
38.0 sVisually, the page fills in at 38.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 101.0 s
101.0 sThe page becomes fully interactive after 101.0 s. Good is under 3.8 s.
Largest Contentful Paint: 8.6 s
8.6 sYour largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ক্যারিয়ার যাত্রা শুরু করুন এখনই:”.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 324 ms
324 msReal visitors wait 324 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 26% slower for real visitors
+26%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 175 ms to 223 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 456 ms
456 msScripts block taps and scrolling for 456 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.007
0.007The layout barely moves while loading (CLS 0.007, good is under 0.1).
Images and page weight
Page weight: 19.8 MB in 349 requests
19.8 MBYour homepage downloads 19.8 MB in 349 requests on a phone: scripts 14.3 MB (130), images 2.4 MB (43) and HTML 1.2 MB (17). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
Digital_growth.png weighs 841 KiB. On a phone connection a single image that size takes seconds.
4 images far larger than shown
532 KiB4 images are downloaded at several times the size a phone draws them, for example Digital_growth.png at 1,150 px wide, shown at 342 px. Resized copies would save about 532 KiB.
12 images in older formats
12 images (1.4 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.
6 images below the first screen load straight away
6 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.6 g of CO₂ per visit
5.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.61 g of CO₂e: 673.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
17 tap targets too small
17 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.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (34 elements)
All page content should be contained by landmarks: 34 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.
17 links without text
17 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is long (100 characters)
Your title is 100 characters, so Google will cut it off around 60: “হোম - eShikhon.com - ইশিখন.কম | Top Best Online Freelancing Training Courses Institute in…”.
2 H1 headlines
There are 2 <h1> headlines (“নতুন Skill শেখার পরিকল্পনা করছেন?” and “প্রিয় মেন্টরদের লাইভ ক্লাস”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
159 internal links, 15 external
The homepage links to 159 pages on eshikhon.com.bd and 15 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://eshikhon.com.bd/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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://eshikhon.com.bd/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://eshikhon.com.bd/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 name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (771 words), so crawlers that don't run JavaScript still read it.
Other pages
12 pages without a meta description
https://eshikhon.com.bd/courses, https://eshikhon.com.bd/it-video-course, https://eshikhon.com.bd/asset-project-%e0%a6%85%e0%a7%8d%e0%a6%af%e0%a6%be%e0%a6%b8%e0%a7%87%e0%a6%9f-%e0%a6%aa%e0%a7%8d%e0%a6%b0%e0%a6%9c%e0%a7%87%e0%a6%95%e0%a7%8d%e0%a6%9f-%e0%a6%b8%e0%a6%b0%e0%a6%95%e0%a6%be%e0%a6%b0, https://eshikhon.com.bd/industrial-attachment, https://eshikhon.com.bd/rpl and https://eshikhon.com.bd/blog and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://eshikhon.com.bd/asset-project-%e0%a6%85%e0%a7%8d%e0%a6%af%e0%a6%be%e0%a6%b8%e0%a7%87%e0%a6%9f-%e0%a6%aa%e0%a7%8d%e0%a6%b0%e0%a6%9c%e0%a7%87%e0%a6%95%e0%a7%8d%e0%a6%9f-%e0%a6%b8%e0%a6%b0%e0%a6%95%e0%a6%be%e0%a6%b0, whose canonical is https://eshikhon.com.bd/asset-project-%E0%A6%85%E0%A7%8D%E0%A6%AF%E0%A6%BE%E0%A6%B8%E0%A7%87%E0%A6%9F-%E0%A6%AA%E0%A7%8D%E0%A6%B0%E0%A6%9C%E0%A7%87%E0%A6%95%E0%A7%8D%E0%A6%9F-%E0%A6%B8%E0%A6%B0%E0%A6%95%E0%A6%BE%E0%A6%B0. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://eshikhon.com.bd/free-courses and https://eshikhon.com.bd/contact have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 59 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
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 broken images
3 images failed to load on a phone, for example https://demos.wplms.io/oneinstructor/wp-content/uploads/2023/08/icon1.png.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
3 small tap targets
3 of 11 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 “grid is not defined”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 597 words of copy
The homepage carries about 597 words of visible text.
4 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Apply RPL”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Meta Pixel and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 4 phone links and 0 email links.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads 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.
9 cookies set on arrival
9Opening the homepage sets 9 cookies, 1 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.
18 other companies contacted
Loading the homepage contacts 18 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 eshikhon.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
- CMS
- WordPress
- Framework
- React
- E-commerce
- WooCommerce
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 54 issues on eshikhon.com.bd, including 25 speed issues, 5 SEO issues and 2 conversion gaps. 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.