Website review, no card needed

contentspeed.ro logo

contentspeed.ro website review

Visit site (opens in a new tab)Reviewed 6 November 202648 issues · 94 checks

This review found 48 issues worth fixing on contentspeed.ro, 21 of them high impact, across 94 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.9 s2.1 sMay 16Oct 312.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.8 s
May 23, 20262.7 s
May 30, 20262.7 s
Jun 6, 20262.6 s
Jun 13, 20262.5 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.7 s
Jul 18, 20262.7 s
Jul 25, 20262.6 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.3 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Oct 24, 20262.3 s
Oct 31, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
186 ms158 msMay 16Oct 31164 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026167 ms
May 23, 2026183 ms
May 30, 2026183 ms
Jun 6, 2026169 ms
Jun 13, 2026171 ms
Jun 20, 2026163 ms
Jun 27, 2026164 ms
Jul 4, 2026170 ms
Jul 11, 2026169 ms
Jul 18, 2026170 ms
Jul 25, 2026162 ms
Aug 1, 2026162 ms
Aug 8, 2026163 ms
Aug 15, 2026166 ms
Aug 22, 2026177 ms
Aug 29, 2026183 ms
Sep 5, 2026178 ms
Sep 12, 2026171 ms
Sep 19, 2026165 ms
Sep 26, 2026162 ms
Oct 3, 2026165 ms
Oct 10, 2026169 ms
Oct 17, 2026161 ms
Oct 24, 2026161 ms
Oct 31, 2026164 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

Full-page screenshot of contentspeed.ro (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. contentspeed.ro at 0.4 s0.4 s
  2. contentspeed.ro at 0.9 s0.9 s
  3. contentspeed.ro at 1.3 s1.3 s
  4. contentspeed.ro at 1.7 s1.7 s
  5. contentspeed.ro at 2.2 s2.2 s
  6. contentspeed.ro at 2.6 s2.6 s
  7. contentspeed.ro at 3.0 s3.0 s
  8. contentspeed.ro at 3.5 s3.5 s

Speed

11 to fix31
  • Use efficient cache lifetimes

    4.8 s · 2.1 MB

    65 files are served with short cache lifetimes, so returning visitors download them again (2.1 MB).

  • Improve image delivery

    3.3 s · 1.5 MB

    20 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.3 s faster on a phone.

  • Reduce unused JavaScript

    3.0 s · 554 KiB

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

  • Render-blocking requests

    1.5 s

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

  • Mobile performance score: 31

    31/100

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

  • Reduce unused CSS

    830 ms · 261 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Hotjar and others), adding 1.3 MB and 802 ms of main-thread time.

  • Google Tag Manager adds 369 ms

    369 ms

    Google Tag Manager costs a phone 369 ms of main-thread work and 536 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.

  • Main-thread work: 2.0 s

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

  • Facebook adds 168 ms

    168 ms

    Facebook costs a phone 168 ms of main-thread work and 318 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.

  • FontAwesome CDN adds 60 ms

    60 ms

    FontAwesome CDN costs a phone 60 ms of main-thread work and 318 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.

  • 10 long tasks on the main thread

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

  • Font display

    150 ms

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

  • Minify JavaScript

    80 ms · 10 KiB

    10 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    24 KiB

    Polyfills for old browsers add 24 KiB JavaScript that modern phones do not need.

  • 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 263 ms

    263 ms

    Your server sent the HTML in 263 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user CLS: 0.41

    0.41

    For real visitors the layout shifts by 0.41 (75th percentile). Good is under 0.1.

  • Largest Contentful Paint: 21.4 s

    21.4 s

    Your largest element takes 21.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Platforma de eCommerce aleasa de liderii pietei”.

  • Time to Interactive: 21.8 s

    21.8 s

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

  • Speed Index: 8.9 s

    8.9 s

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

  • Cumulative Layout Shift: 0.443

    0.443

    The layout shifts by 0.443 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Real-user TTFB: 852 ms

    852 ms

    Real visitors wait 852 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • 50 images without width and height

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

  • Total Blocking Time: 371 ms

    371 ms

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

  • Tap response (INP) held steady for real visitors

    -7%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 167 ms to 164 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

    Real visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 169 ms

    169 ms

    Real visitors wait 169 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 1.6 s

    1.6 s

    Real visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.

  • Largest content (LCP) got 17% faster for real visitors

    -17%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Images and page weight

4 to fix53
  • 2 images over 500 KB

    2 images weigh 1.5 MB together. On a phone connection a single image that size takes seconds.

  • Page weight: 3.8 MB in 130 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 130 requests on a phone: images 1.9 MB (59), scripts 1.3 MB (35) and fonts 336 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (1.5 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.

  • 3 images below the first screen load straight away

    3 images further down the page (725 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.1 g of CO₂ per visit

    1.09 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.09 g of CO₂e: 130.4 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

11 to fixGoogle 5781
  • 20 buttons without a name

    20 buttons have no accessible name, so screen readers announce just “button”.

  • Active <area> elements must have alternative text (3 elements)

    Active <area> elements must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.

  • 4 text elements with low contrast

    4 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.

  • 7 images without alt text

    7 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (51 elements)

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

  • Zoom is disabled

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

  • 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.

  • 11 links without text

    11 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.

1 checks passed
  • 31 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 11 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 7771
  • 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 long (81 characters)

    Your title is 81 characters, so Google will cut it off around 60: “Creare magazin online la cheie pe o platforma ecommerce romaneasca - ContentSpeed”.

  • 6 links crawlers can't follow

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

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • 162 internal links, 11 external

    The homepage links to 162 pages on contentspeed.ro and 11 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.contentspeed.ro/.

  • Structured data in place

    Structured data found: WebPage.

  • 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.contentspeed.ro/sitemap-index.xml.

AI search readiness

1 to fix88
  • 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.contentspeed.ro/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 (1,022 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://www.contentspeed.ro/startup/module/abonamente-saas is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://www.contentspeed.ro/platforma-ecommerce, https://www.contentspeed.ro/portal-b2b and https://www.contentspeed.ro/demo-magazin-online have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages slow to respond

    https://www.contentspeed.ro/startup/module/functionalitati/functionalitati-avansate, https://www.contentspeed.ro/startup/module/functionalitati/relatia-cu-clientii, https://www.contentspeed.ro/startup/module/functionalitati/module-ecommerce and https://www.contentspeed.ro/startup/module/functionalitati/marketing-si-promovare took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9676
  • 1 broken image

    1 image failed to load on a phone, for example https://www.contentspeed.ro/.

  • 22 small tap targets

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

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • Local business without LocalBusiness data

    Your homepage shows a map 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 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 723 words of copy

    The homepage carries about 723 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Demo Gratuit!”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact” and “Demo Gratuit!”.

  • Social proof on the page

    Social proof on the homepage: 8 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and Hotjar.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 1 more (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.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies, 1 of them by other companies (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.

  • 23 other companies contacted

    Loading the homepage contacts 23 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 contentspeed.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
jQuery
Analytics
Google Tag Manager | Hotjar

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on contentspeed.ro, including 21 speed issues, 4 SEO issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25