Website review, no card needed
fbexpress.pk website review
Visit site (opens in a new tab)Reviewed 22 November 202625 issues · 75 checks
This review found 25 issues worth fixing on fbexpress.pk, 6 of them high impact, across 75 checks. The most urgent: fails Core Web Vitals for real visitors. 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
83B- #28,426 of 125,263 reviewed websitesbeats 72%
- #18,516 of 70,145 online storesbeats 67%
- #17,925 of 63,741 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 816 ms |
| Jun 6, 2026 | 831 ms |
| Jun 13, 2026 | 836 ms |
| Jun 20, 2026 | 883 ms |
| Jun 27, 2026 | 943 ms |
| Jul 4, 2026 | 1.0 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 894 ms |
| Oct 10, 2026 | 862 ms |
| Oct 17, 2026 | 837 ms |
| Oct 24, 2026 | 814 ms |
| Oct 31, 2026 | 817 ms |
| Nov 7, 2026 | 796 ms |
| Nov 14, 2026 | 774 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 233 ms |
| Jun 6, 2026 | 239 ms |
| Jun 13, 2026 | 239 ms |
| Jun 20, 2026 | 245 ms |
| Jun 27, 2026 | 272 ms |
| Jul 4, 2026 | 288 ms |
| Jul 11, 2026 | 302 ms |
| Jul 18, 2026 | 304 ms |
| Jul 25, 2026 | 314 ms |
| Aug 1, 2026 | 351 ms |
| Aug 8, 2026 | 382 ms |
| Aug 15, 2026 | 421 ms |
| Aug 22, 2026 | 442 ms |
| Aug 29, 2026 | 427 ms |
| Sep 5, 2026 | 423 ms |
| Sep 12, 2026 | 405 ms |
| Sep 19, 2026 | 405 ms |
| Sep 26, 2026 | 393 ms |
| Oct 3, 2026 | 358 ms |
| Oct 10, 2026 | 357 ms |
| Oct 17, 2026 | 339 ms |
| Oct 24, 2026 | 330 ms |
| Oct 31, 2026 | 330 ms |
| Nov 7, 2026 | 316 ms |
| Nov 14, 2026 | 303 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
5,236 HTML elements
The page has 5,236 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Render-blocking requests
500 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Reduce unused CSS
26 KiBAbout 26 KiB of CSS is downloaded but never applied on this page.
2 third-party services on the page
2 third-party services load with your homepage (Shopify and Google Fonts), adding 136 KiB and 6 ms of main-thread time.
Improve image delivery
18 KiB1 image could be 18 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
Use efficient cache lifetimes
1 KiB1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).
3 checks passed
Mobile performance score: 99
99/100Your mobile performance score is 99. That is in Google's “good” band (90 and up).
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 136 ms of it running JavaScript. That is comfortably low.
Server response: 23 ms
23 msYour server sent the HTML in 23 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.
Real-user INP: 348 ms
348 msReal visitors wait 348 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 31% slower for real visitors
+31%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 233 ms to 303 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 910 ms
910 msReal visitors wait 910 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.5 s
3.5 sVisually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
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).
Largest Contentful Paint: 1.2 s
1.2 sYour largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “🔄”.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Time to Interactive: 1.2 s
1.2 sThe page is fully interactive after 1.2 s.
Images and page weight
3 images far larger than shown
48 KiB3 images are downloaded at several times the size a phone draws them, for example 1000248280_600x600_crop_center.jpg at 600 px wide, shown at 171 px. Resized copies would save about 48 KiB.
About 0.3 g of CO₂ per visit
0.28 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.28 g of CO₂e: 34.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1,024 KiB in 80 requests
1,024 KiBYour homepage downloads 1,024 KiB in 80 requests on a phone: images 531 KiB (17), scripts 224 KiB (22) and stylesheets 134 KiB (37). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
20 text elements with low contrast
20 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (14 elements)
All page content should be contained by landmarks: 14 elements on the page fail this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
32 form fields without a label
32 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (10 elements)
Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 75 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “FB Express Online | Eastern & Western Fashion for Kids – Fbexpress”.
184 internal links, 7 external
The homepage links to 184 pages on fbexpress.pk and 7 external pages.
7 checks passed
Meta description: 143 characters
Your meta description is 143 characters: “Shop trendy kids & fashion collections at FB Express Online. Premium styles, affordable prices, fast delivery & excitin…”.
One H1 headline
Your main headline reads: “Fbexpress”.
Canonical URL set
The canonical URL is https://fbexpressonline.com/.
Structured data in place
Structured data found: 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://fbexpressonline.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (3,117 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://fbexpressonline.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://fbexpressonline.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://fbexpressonline.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
11 pages without a meta description
https://fbexpressonline.com/customer_authentication/redirect, https://fbexpressonline.com/collections/boys, https://fbexpressonline.com/collections/girls, https://fbexpressonline.com/collections/kid, https://fbexpressonline.com/collections/babies and https://fbexpressonline.com/collections/last-piece-alert and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
11 pages without an H1
https://fbexpressonline.com/customer_authentication/redirect, https://fbexpressonline.com/collections/boys, https://fbexpressonline.com/collections/girls, https://fbexpressonline.com/collections/kid, https://fbexpressonline.com/collections/babies and https://fbexpressonline.com/collections/last-piece-alert and 5 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 93 found) and read each the way a search engine does.
3 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.
Best practices
14 small tap targets
14 of 50 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
Thin social proof
Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
A 53-field form
Your longest form asks for 53 fields (0 required). Every extra field lowers completion.
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 626 words of copy
The homepage carries about 626 words of visible text.
2 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Shop All Deals”, “Contact” and “Subscribe”.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
Privacy and tracking
5 cookies set on arrival
5Opening the homepage sets 5 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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 fbexpress.pk, 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 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Meteor Mega Menu · Musbu Wa Chat · Bacon Menu
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
- The footer still says © 2024.
Stack
- 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 25 issues on fbexpress.pk, including 7 speed issues, 1 SEO issue 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.