qbslearning.com website review

46 files block the first paint until they finish downloading. Deferring or inlining them could save about 22.7 s.

About 2.4 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 12.4 s faster on a phone.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.8 s).

Your mobile performance score is 34 (desktop: 25). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

6 third-party services load with your homepage (Google CDN, Facebook and Google Tag Manager and others), adding 1.3 MB and 1.5 s of main-thread time.

213 KiB could be saved by minifying CSS.

2 images could be 236 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

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

183 KiB could be saved by minifying JavaScript.

Google CDN costs a phone 773 ms of main-thread work and 734 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.

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

Facebook costs a phone 383 ms of main-thread work and 212 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 Tag Manager costs a phone 341 ms of main-thread work and 177 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.

Polyfills for old browsers add 40 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

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.

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

Your largest element takes 37.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Decades of Excellence in building Innovative Educational Pr…”.

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

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

Scripts block taps and scrolling for 932 ms in total while the page loads. Good is under 200 ms.

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

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 6.4 MB in 118 requests on a phone: scripts 2.6 MB (56), stylesheets 2.6 MB (39) and images 769 KiB (6). Under 2 MB keeps phones on slow connections fast.

1 image (261 KiB) is 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.82 g of CO₂e: 218.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

24 tap targets are too small or too close together to hit reliably with a finger.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Elements marked as presentational should be consistently ignored: 21 elements on the page fail this check, rated minor by axe-core.

7 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your title is 73 characters, so Google will cut it off around 60: “QBS Learning | Developing and Innovating Educational Experiences Globally”.

Your meta description is 248 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.

There is no robots.txt at qbslearning.com/robots.txt, the first file search crawlers ask for.

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

1 link has no real href, so search engines can't follow it.

Your <h1> is empty.

The homepage links to 109 pages on qbslearning.com and 15 external pages.

There is no https://qbslearning.com/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.

Your homepage links to https://qbslearning.com/ai-copilot, which answers with an error. Visitors hit a dead end and search engines drop it.

https://qbslearning.com/creative-services and https://qbslearning.com/services/creative-services all use the title “Creative Designing | Book Designing Services - QBS Learning”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://qbslearning.com/creative-services and https://qbslearning.com/services/creative-services use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://qbslearning.com/services/creative-services, whose canonical is https://qbslearning.com/creative-services. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://qbslearning.com/content-development and https://qbslearning.com/content-development/assessment have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 of 7 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'setAttribute')”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: “500+ Happy Customers”. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 397 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads 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 3 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 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.