Website review, no card needed
deltatelgroup.com website review
Visit site (opens in a new tab)Reviewed 4 November 202645 issues · 76 checks
This review found 45 issues worth fixing on deltatelgroup.com, 15 of them high impact, across 76 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
64DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.1 s
2.2 s
3.3 s
4.5 s
5.6 s
6.7 s
7.8 s
8.9 s
Speed
Use efficient cache lifetimes
6.7 s · 2.7 MB67 files are served with short cache lifetimes, so returning visitors download them again (2.7 MB).
Render-blocking requests
2.2 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.2 s.
Improve image delivery
500 ms · 973 KiB12 images could be 973 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Reduce unused CSS
900 ms · 133 KiBAbout 133 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Font display
800 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 800 ms).
Minify JavaScript
300 ms · 12 KiB12 KiB could be saved by minifying JavaScript.
Minify CSS
150 ms · 11 KiB11 KiB could be saved by minifying CSS.
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 third-party service on the page
1 third-party service load with your homepage (integraldesign.ro), adding 3 KiB and 0 ms of main-thread time.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 192 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.4 s
13.4 sYour largest element takes 13.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Telecom and infrastructure”. Most of its time is resource load delay (6.5 s).
Speed Index: 12.3 s
12.3 sVisually, the page fills in at 12.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 13.7 s
13.7 sThe page becomes fully interactive after 13.7 s. Good is under 3.8 s.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
32 images without width and height
32 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.121
0.121The layout shifts by 0.121 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Not enough real-visitor data yet
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.
1 checks passed
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.7 MB in 68 requests
2.7 MBYour homepage downloads 2.7 MB in 68 requests on a phone: images 1.7 MB (29), fonts 617 KiB (4) and scripts 218 KiB (24). Under 2 MB keeps phones on slow connections fast.
8 images in older formats
8 images (1.6 MB) are 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.
6 images below the first screen load straight away
6 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.78 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.78 g of CO₂e: 93.5 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
20 buttons without a name
20 buttons have no accessible name, so screen readers announce just “button”.
19 tap targets too small
19 tap targets are too small or too close together to hit reliably with a finger.
16 text elements with low contrast
16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
9 images without alt text
9 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 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.
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.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (5 elements)
ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.
1 checks passed
35 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: 35 passed and 10 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (21 characters)
Your title is only 21 characters: “Home - Deltatel Group”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
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://deltatelgroup.com/sitemap.xml, so Google discovers your pages only by following links.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
31 internal links, 1 external
The homepage links to 31 pages on deltatelgroup.com and 1 external page.
1 checks passed
robots.txt in place
robots.txt is in place.
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://deltatelgroup.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 (763 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://deltatelgroup.com/en and / all use the title “Home - Deltatel Group”. Search engines can't tell which page to show for a search, so each competes with the others.
13 pages without a meta description
https://deltatelgroup.com/ro, https://deltatelgroup.com/en/solutions/telecommunications, https://deltatelgroup.com/en/solutions/software-professional-services, https://deltatelgroup.com/en/solutions/vertical-market, https://deltatelgroup.com/en/company and https://deltatelgroup.com/en/careers and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://deltatelgroup.com/ro and / have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://deltatelgroup.com/en/careers 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.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 13 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
8 small tap targets
8 of 18 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Cannot redefine property: cookie Object.defineProperty (<anonymous>)”.
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 694 words of copy
The homepage carries about 694 words of visible text.
1 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact”.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
1 other company contacted
Loading the homepage contacts 1 host 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 deltatelgroup.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Joomla
- Framework
- jQuery
- Hosting
- Eta2u As Sc Eta2u Srl
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 deltatelgroup.com, including 13 speed issues, 9 SEO issues 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.