Website review, no card needed
actycrea.com website review
Visit site (opens in a new tab)Reviewed 18 November 202633 issues · 76 checks
This review found 33 issues worth fixing on actycrea.com, 16 of them high impact, across 76 checks. The most urgent: reduce unused JavaScript. 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
68DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Reduce unused JavaScript
4.6 s · 894 KiBAbout 894 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.6 s faster on a phone.
Render-blocking requests
1.4 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 47
47/100Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7 third-party services on the page
7 third-party services load with your homepage (YouTube, Google Tag Manager and termly.io and others), adding 1.5 MB and 884 ms of main-thread time.
Use efficient cache lifetimes
600 ms · 118 KiB3 files are served with short cache lifetimes, so returning visitors download them again (118 KiB).
Minify JavaScript
600 ms · 115 KiB115 KiB could be saved by minifying JavaScript.
Improve image delivery
450 ms · 239 KiB5 images could be 239 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
YouTube adds 507 ms
507 msYouTube costs a phone 507 ms of main-thread work and 1,000 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: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 242 ms
242 msGoogle Tag Manager costs a phone 242 ms of main-thread work and 322 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.
Reduce unused CSS
280 ms · 132 KiBAbout 132 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 219 ms. During a long task the page ignores taps.
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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 17.5 s
17.5 sYour largest element takes 17.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use essential cookies to make our site work. With your c…”.
Time to Interactive: 17.8 s
17.8 sThe page becomes fully interactive after 17.8 s. Good is under 3.8 s.
Speed Index: 10.0 s
10.0 sVisually, the page fills in at 10.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 750 ms
750 msScripts block taps and scrolling for 750 ms in total while the page loads. Good is under 200 ms.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
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.
2 checks passed
Cumulative Layout Shift: 0.058
0.058The layout barely moves while loading (CLS 0.058, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 22.3 MB in 86 requests
22.3 MBYour homepage downloads 22.3 MB in 86 requests on a phone: media 18.7 MB (8), scripts 1.7 MB (18) and images 1.5 MB (27). Under 2 MB keeps phones on slow connections fast.
8 images far larger than shown
683 KiB8 images are downloaded at several times the size a phone draws them, for example home-luis-mario.webp at 1,000 px wide, shown at 195 px. Resized copies would save about 683 KiB.
13 images below the first screen load straight away
13 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (119 KiB) 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.
About 6.3 g of CO₂ per visit
6.33 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.33 g of CO₂e: 759.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
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.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 5 failed. 3 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 short (23 characters)
Your title is only 23 characters: “Home - Actycrea.Studio®”. Between 30 and 65 characters leaves room to say what you do and for whom.
19 internal links, 1 external
The homepage links to 19 pages on actycrea.com and 1 external page.
6 checks passed
Meta description: 81 characters
Your meta description is 81 characters: “Estudio de diseño, estrategia y mucha tecnología para marcas y humanos digitales.”.
Canonical URL set
The canonical URL is https://actycrea.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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://actycrea.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://actycrea.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.
3 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (367 words), so crawlers that don't run JavaScript still read it.
Other pages
10 pages without a meta description
https://actycrea.com/contacto, https://actycrea.com/studio, https://actycrea.com/proyectos/la-tienda-de-los-musicales, https://actycrea.com/proyectos/martin-millers-gin, https://actycrea.com/proyectos/grenergy and https://actycrea.com/proyectos/zamora-company and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
4 links to non-canonical URLs
Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://actycrea.com/proyectos/la-tienda-de-los-musicales, whose canonical is https://actycrea.com/case/la-tienda-de-los-musicales. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages without an H1
https://actycrea.com/proyectos, https://actycrea.com/contacto, https://actycrea.com/studio and https://actycrea.com/servicios have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://actycrea.com/contacto 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.
4 pages slow to respond
https://actycrea.com/servicios, https://actycrea.com/proyectos/la-tienda-de-los-musicales, https://actycrea.com/proyectos/martin-millers-gin and https://actycrea.com/proyectos/grenergy took over 3 s to send their HTML from our server.
12 internal pages checked
We fetched 12 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 12 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
3 small tap targets
3 of 8 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 409 words of copy
The homepage carries about 409 words of visible text.
3 checks passed
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and 4 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
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). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.
7 cookies set on arrival
7Opening the homepage sets 7 cookies, 1 of them by other companies (measured from a US location before any click).
12 other companies contacted
Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Termly
A consent management tool (Termly) 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 actycrea.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
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- DinaHosting S.L.
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 actycrea.com, including 15 speed issues, 2 SEO issues and 2 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.