Website review, no card needed
myelala.com website review
Visit site (opens in a new tab)Reviewed 11 November 202635 issues · 74 checks
This review found 35 issues worth fixing on myelala.com, 8 of them high impact, across 74 checks. The most urgent: page weight: 40.6 MB in 327 requests. 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
One score from every part of this review. How it works
Speed
Render-blocking requests
1.2 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, chatty.net and Google CDN and others), adding 11.6 MB and 156 ms of main-thread time.
Shopify adds 79 ms
79 msShopify costs a phone 79 ms of main-thread work and 11.4 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.
Mobile performance score: 80
80/100Your mobile performance score is 80. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
150 ms · 570 KiB18 images could be 570 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused JavaScript
326 KiBAbout 326 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
316 KiB11 files are served with short cache lifetimes, so returning visitors download them again (316 KiB).
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 541 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 62 ms. During a long task the page ignores taps.
Reduce unused CSS
11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
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: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 5.1 s
5.1 sYour largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 9.1 s
9.1 sThe page becomes fully interactive after 9.1 s. Good is under 3.8 s.
Speed Index: 3.6 s
3.6 sVisually, the page fills in at 3.6 s (Speed Index). Good is under 3.4 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
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.
3 checks passed
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 6 ms
6 msScripts block the page for only 6 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 40.6 MB in 327 requests
40.6 MBYour homepage downloads 40.6 MB in 327 requests on a phone: media 38.0 MB (12), other files 1.1 MB (192) and scripts 712 KiB (64). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
M-638x870.jpg 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).
3 images far larger than shown
387 KiB3 images are downloaded at several times the size a phone draws them, for example unionpay-logo.jpg at 1,024 px wide, shown at 37 px. Resized copies would save about 387 KiB.
6 images below the first screen load straight away
6 images further down the page (486 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
4 images in older formats
4 images (430 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 11.5 g of CO₂ per visit
11.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 11.52 g of CO₂e: 1382.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
22 links without text
22 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
Table header text should not be empty (1 element)
Table header text should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
<td> elements in a large <table> do not have table headers.
<td> elements in a large <table> do not have table headers. (1 element).
1 checks passed
55 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 55 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (15 characters)
Your title is only 15 characters: “Elala Home Page”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (278 characters)
Your meta description is 278 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
One H1 headline
Your <h1> is empty.
67 internal links, 20 external
The homepage links to 67 pages on myelala.com and 20 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://myelala.com/.
Structured data in place
Structured data found: Organization 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://myelala.com/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: 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 (472 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://myelala.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
9 pages without a meta description
https://myelala.com/pages/our-collection, https://myelala.com/collections/elala-master, https://myelala.com/collections/elala-premium-edition, https://myelala.com/collections/elala-pet-carrier, https://myelala.com/pages/official-store-china and https://myelala.com/pages/e-commerce-store and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
12 pages without an H1
https://myelala.com/pages/our-collection, https://myelala.com/collections/elala-master, https://myelala.com/collections/essential, https://myelala.com/collections/elala-lite, https://myelala.com/collections/elala-premium-edition and https://myelala.com/collections/elala-pet-carrier and 6 others 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 27 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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
1 broken image
1 image failed to load on a phone, for example https://www.bankislam.com/wp-content/uploads/duitnow_400x246.jpg.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
8 distorted images
8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
Tap targets are thumb-sized
25 of 27 tappable elements near the top are at least 24 px.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 281 words of copy
The homepage carries about 281 words of visible text.
2 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Shops for Order Pick Up”, “Contact Us” and “JOIN NOW”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel and TikTok 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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
25 other companies contacted
Loading the homepage contacts 25 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 myelala.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pagefly Ai Page Builder · Avada Faqs · Forms · nice-team.net · nfcube.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on myelala.com, including 12 speed issues, 4 SEO issues and 4 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.