Website review, no card needed
orange.ro website review
Visit site (opens in a new tab)Reviewed 28 October 202633 issues · 84 checks
This review found 33 issues worth fixing on orange.ro, 7 of them high impact, across 84 checks. The most urgent: render-blocking 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
Site score
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.7 s |
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 245 ms |
| May 16, 2026 | 238 ms |
| May 23, 2026 | 230 ms |
| May 30, 2026 | 224 ms |
| Jun 6, 2026 | 221 ms |
| Jun 13, 2026 | 221 ms |
| Jun 20, 2026 | 221 ms |
| Jun 27, 2026 | 221 ms |
| Jul 4, 2026 | 222 ms |
| Jul 11, 2026 | 221 ms |
| Jul 18, 2026 | 220 ms |
| Jul 25, 2026 | 217 ms |
| Aug 1, 2026 | 216 ms |
| Aug 8, 2026 | 219 ms |
| Aug 15, 2026 | 223 ms |
| Aug 22, 2026 | 228 ms |
| Aug 29, 2026 | 230 ms |
| Sep 5, 2026 | 230 ms |
| Sep 12, 2026 | 230 ms |
| Sep 19, 2026 | 229 ms |
| Sep 26, 2026 | 227 ms |
| Oct 3, 2026 | 226 ms |
| Oct 10, 2026 | 223 ms |
| Oct 17, 2026 | 222 ms |
| Oct 24, 2026 | 222 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
Speed
Render-blocking requests
2.8 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.
Improve image delivery
350 ms · 955 KiB19 images could be 955 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Mobile performance score: 71
71/100Your mobile performance score is 71 (desktop: 88). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
150 ms · 349 KiBAbout 349 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
7 third-party services on the page
7 third-party services load with your homepage (cookiepro.com, Google Tag Manager and mydigitalorange.ro and others), adding 2.2 MB and 163 ms of main-thread time.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Other Google APIs/SDKs adds 0 ms
0 msOther Google APIs/SDKs costs a phone 0 ms of main-thread work and 1.8 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 212 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 55 KiBAbout 55 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
62 KiBPolyfills for old browsers add 62 KiB JavaScript that modern phones do not need.
Use efficient cache lifetimes
54 KiB5 files are served with short cache lifetimes, so returning visitors download them again (54 KiB).
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.
1 checks passed
Server response: 132 ms
132 msYour server sent the HTML in 132 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 9.3 s
9.3 sVisually, the page fills in at 9.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 13.2 s
13.2 sThe page becomes fully interactive after 13.2 s. Good is under 3.8 s.
Largest Contentful Paint: 3.6 s
3.6 sYour largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Total Blocking Time: 315 ms
315 msScripts block taps and scrolling for 315 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 245 ms to 222 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 173 ms
173 msReal visitors wait 173 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.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 391 ms
391 msReal visitors wait 391 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.015
0.015The layout barely moves while loading (CLS 0.015, good is under 0.1).
Images and page weight
Page weight: 3.3 MB in 108 requests
3.3 MBYour homepage downloads 3.3 MB in 108 requests on a phone: images 1.9 MB (54), scripts 1.1 MB (19) and fonts 114 KiB (3). Under 2 MB keeps phones on slow connections fast.
5 images far larger than shown
208 KiB5 images are downloaded at several times the size a phone draws them, for example 1787725601_0caea6ba780088eb8cec.webp at 1,160 px wide, shown at 288 px. Resized copies would save about 208 KiB.
1 image in older formats
1 image (40 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 0.9 g of CO₂ per visit
0.94 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.94 g of CO₂e: 112.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (34 elements)
All page content should be contained by landmarks: 34 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (3 elements)
Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 77 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 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
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “Orange - Cea mai rapida retea | Abonamente Voce & Date | Internet | TV”.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
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
No XML sitemap at https://www.orange.ro/help/upload/sitemap.xml, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
96 internal links, 27 external
The homepage links to 96 pages on orange.ro and 27 external pages.
3 checks passed
Meta description: 127 characters
Your meta description is 127 characters: “Servicii de telefonie mobila, voce fixa, televiziune prin cablu si internet prin fibra la cele mai bune preturi. Vezi o…”.
Structured data in place
Structured data found: Organization.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (517 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.orange.ro/llms.txt (6 KiB, 36 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.orange.ro/oferte-speciale/back-to-school is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://www.orange.ro/magazin-online and https://www.orange.ro/magazin-online/telefoane all use the title “Orange Magazin Online”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://www.orange.ro/help, https://www.orange.ro/contact, https://www.orange.ro/magazin-online and https://www.orange.ro/magazin-online/telefoane have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages without an H1
https://www.orange.ro/help, https://www.orange.ro/contact, https://www.orange.ro/shops, https://www.orange.ro/magazin-online, https://www.orange.ro/business and https://www.orange.ro/magazin-online/telefoane have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://www.orange.ro/help and https://www.orange.ro/magazin-online took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 44 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
7 distorted images
7 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
38 of 38 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.
Local business without LocalBusiness data
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 597 words of copy
The homepage carries about 597 words of visible text.
5 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact”.
1 short form
A short form (2 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
16 cookies set on arrival
16Opening the homepage sets 16 cookies (measured from a US location before any click).
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 orange.ro, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Tag Manager
- Hosting
- Asn Orange Romania
Company
- Employees
- 3,931
- Founded
- 1996
- Headquarters
- Bucharest
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on orange.ro, including 12 speed issues, 5 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.