Website review, no card needed
orangetee.com website review
Visit site (opens in a new tab)Reviewed 4 November 202645 issues · 91 checks
This review found 45 issues worth fixing on orangetee.com, 16 of them high impact, across 91 checks. The most urgent: use efficient cache lifetimes. 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
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 636 ms |
| May 23, 2026 | 651 ms |
| May 30, 2026 | 780 ms |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 902 ms |
| Jun 20, 2026 | 889 ms |
| Jun 27, 2026 | 871 ms |
| Jul 4, 2026 | 788 ms |
| Jul 11, 2026 | 794 ms |
| Jul 18, 2026 | 785 ms |
| Jul 25, 2026 | 708 ms |
| Aug 1, 2026 | 778 ms |
| Aug 8, 2026 | 778 ms |
| Aug 15, 2026 | 803 ms |
| Aug 22, 2026 | 938 ms |
| Aug 29, 2026 | 950 ms |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 969 ms |
| Sep 19, 2026 | 783 ms |
| Sep 26, 2026 | 667 ms |
| Oct 3, 2026 | 643 ms |
| Oct 10, 2026 | 702 ms |
| Oct 17, 2026 | 874 ms |
| Oct 24, 2026 | 1.0 s |
| Oct 31, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 78 ms |
| May 23, 2026 | 78 ms |
| May 30, 2026 | 78 ms |
| Jun 6, 2026 | 86 ms |
| Jun 13, 2026 | 80 ms |
| Jun 20, 2026 | 85 ms |
| Jun 27, 2026 | 79 ms |
| Jul 4, 2026 | 77 ms |
| Jul 11, 2026 | 77 ms |
| Jul 18, 2026 | 76 ms |
| Jul 25, 2026 | 79 ms |
| Aug 1, 2026 | 80 ms |
| Aug 8, 2026 | 79 ms |
| Aug 15, 2026 | 79 ms |
| Aug 22, 2026 | 74 ms |
| Aug 29, 2026 | 72 ms |
| Sep 5, 2026 | 71 ms |
| Sep 12, 2026 | 74 ms |
| Sep 19, 2026 | 77 ms |
| Sep 26, 2026 | 76 ms |
| Oct 3, 2026 | 75 ms |
| Oct 10, 2026 | 74 ms |
| Oct 17, 2026 | 72 ms |
| Oct 24, 2026 | 80 ms |
| Oct 31, 2026 | 84 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
Use efficient cache lifetimes
6.2 s · 10.1 MB54 files are served with short cache lifetimes, so returning visitors download them again (10.1 MB).
Reduce unused JavaScript
2.3 s · 695 KiBAbout 695 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Render-blocking requests
1.6 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Improve image delivery
650 ms · 2.9 MB17 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.
5 third-party services on the page
5 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.4 MB and 1.0 s of main-thread time.
Mobile performance score: 52
52/100Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.
Google CDN adds 764 ms
764 msGoogle CDN costs a phone 764 ms of main-thread work and 1.1 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.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
170 ms · 49 KiBAbout 49 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 170 ms faster on a phone.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 217 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
8 KiB8 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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.5 s
13.5 sYour largest element takes 13.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Recruitment banner”.
Time to Interactive: 15.2 s
15.2 sThe page becomes fully interactive after 15.2 s. Good is under 3.8 s.
Total Blocking Time: 667 ms
667 msScripts block taps and scrolling for 667 ms in total while the page loads. Good is under 200 ms.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) got 69% slower for real visitors
+69%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.6 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
20 images without width and height
20 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 78 ms to 84 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 104 ms
104 msReal visitors wait 104 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 574 ms
574 msReal visitors wait 574 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 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).
Images and page weight
Page weight: 16.7 MB in 75 requests
16.7 MBYour homepage downloads 16.7 MB in 75 requests on a phone: images 14.7 MB (40), scripts 1.4 MB (15) and other files 353 KiB (4). Under 2 MB keeps phones on slow connections fast.
8 images over 500 KB
8 images weigh 9.6 MB together. On a phone connection a single image that size takes seconds.
4 images below the first screen load straight away
4 images further down the page (301 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (285 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.
About 4.7 g of CO₂ per visit
4.74 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.74 g of CO₂e: 568.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
13 images without alt text
13 images have no alt text, which hurts accessibility and image search.
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.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
Links look like plain text
2 links inside paragraphs rely on colour alone to stand out.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings skip levels
Headings skip levels (h1 → h3, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
12 H1 headlines
There are 12 <h1> headlines (“Explore Property Projects in Singapore and Overse…”, “Explore Property Projects in Singapore and Overse…” and “Our Story”). One clear main headline is easier for people and search engines.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
95 internal links, 14 external
The homepage links to 95 pages on orangetee.com and 14 external pages.
6 checks passed
Meta description: 122 characters
Your meta description is 122 characters: “Property agency providing buy, sell, rent service for your resale, condo homes. For Agents, businesses & property seeke…”.
Title: 52 characters
Your title is a healthy 52 characters: “OrangeTee Real Estate Agency - 25 years in Singapore”.
Canonical URL set
The canonical URL is https://www.orangetee.com/.
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://www.orangetee.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.orangetee.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.
2 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 (981 words), so crawlers that don't run JavaScript still read it.
Other pages
10 pages point its canonical at the homepage
https://www.orangetee.com/Home/OurStory, https://www.orangetee.com/Home/ForAgents, https://www.orangetee.com/Home/Businesses, https://www.orangetee.com/Home/CorporateSolutions, https://www.orangetee.com/Home/BusinessCommercial and https://www.orangetee.com/Home/InvestmentSale and 4 others declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
10 pages share a title
https://www.orangetee.com/Home, https://www.orangetee.com/Home/OurStory, https://www.orangetee.com/Home/ForAgents, https://www.orangetee.com/Home/Businesses, https://www.orangetee.com/Home/CorporateSolutions and https://www.orangetee.com/Home/BusinessCommercial and 4 others all use the title “OrangeTee Real Estate Agency - 25 years in Singapore”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.orangetee.com/Home/EnquireProperty has no meta description, so Google writes the search snippet from whatever text it finds.
10 pages share a meta description
https://www.orangetee.com/Home/OurStory, https://www.orangetee.com/Home/ForAgents, https://www.orangetee.com/Home/Businesses, https://www.orangetee.com/Home/CorporateSolutions, https://www.orangetee.com/Home/BusinessCommercial and https://www.orangetee.com/Home/InvestmentSale and 4 others use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://www.orangetee.com/Landings/Training, https://www.orangetee.com/Landings/Culture and https://www.orangetee.com/Landings/TechTools 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 47 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.
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
10 small tap targets
10 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “a(...).scrollspy is not a function”.
6 distorted images
6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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.
Thin social proof
Social proof on the homepage: “40K+ Happy Customers”. Pairing it with named testimonials or customer logos makes it far more convincing.
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 543 words of copy
The homepage carries about 543 words of visible text.
3 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Join OrangeTee”, “Enquire Property” and “Learn More”.
1 short form
A short form (5 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
6 other companies contacted
Loading the homepage contacts 6 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 orangetee.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on orangetee.com, including 14 speed issues, 3 SEO issues and 3 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.