oksir.com website review

About 761 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.

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

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

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

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

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

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

YouTube costs a phone 844 ms of main-thread work and 967 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.

About 159 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

Facebook costs a phone 393 ms of main-thread work and 210 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 312 ms of main-thread work and 146 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.

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

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

10 KiB could be saved by minifying CSS.

Desktop scores 91 but mobile only 34. A gap that wide usually means heavy scripts and images that hit phones hardest.

7 KiB could be saved by minifying JavaScript.

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 8.1 s on a phone. Good is under 1.8 s.

Your largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Download theApp”. Most of its time is element render delay (11.9 s).

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

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

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

28 images 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 2.0 MB in 194 requests on a phone: scripts 1.6 MB (40), stylesheets 179 KiB (22) and HTML 81 KiB (2). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.57 g of CO₂e: 68.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

1 dropdown has no label.

3 elements hidden from screen readers can still receive keyboard focus.

1 frame has no title, so screen-reader users cannot tell what it contains.

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 36 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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

5 visible links have no text or label, so screen readers cannot say where they go.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your meta description is 184 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (Corporation) but with 1 problem, for example “Corporation: logo is not an absolute URL ("images/oksir-logo-small.png")”.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://oksir.com/sitemap.xml, so Google discovers your pages only by following links.

Your hreflang tags are invalid, so Google may show the wrong language version.

3 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 33 pages on oksir.com and 8 external pages.

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

/ and https://oksir.com/en-hk all use the title “OkSir - Book Verified Home & Local Services Online”. Search engines can't tell which page to show for a search, so each competes with the others.

https://oksir.com/zh-hk, https://oksir.com/en-in, https://oksir.com/business, https://oksir.com/en-hk, https://oksir.com/individual-offers and https://oksir.com/blog and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://oksir.com/zh-hk 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.

https://oksir.com/en-in, https://oksir.com/business and https://oksir.com/en-hk took over 3 s to send their HTML from our server.

We fetched 7 pages linked from your homepage and read each the way a search engine does.

10 images failed to load on a phone, for example https://oksir.com/images/oksir-logo-small.png.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 500 ()”.

Chrome logged issues while loading the page (“Cookie”).

The homepage carries about 458 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight 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 5 cookies, 1 of them by other companies (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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.