Website review, no card needed

Socialpoint logo

socialpoint.es website review

Visit site (opens in a new tab)Reviewed 20 November 202649 issues · 88 checks

This review found 49 issues worth fixing on socialpoint.es, 16 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Socialpoint

  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
5.1 s4.2 sMay 30Nov 144.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20264.7 s
Jun 6, 20264.6 s
Jun 13, 20264.5 s
Jun 20, 20264.6 s
Jun 27, 20264.7 s
Jul 4, 20264.8 s
Jul 11, 20264.9 s
Jul 18, 20265.0 s
Jul 25, 20264.9 s
Aug 1, 20264.8 s
Aug 8, 20264.8 s
Aug 15, 20264.7 s
Aug 22, 20264.6 s
Aug 29, 20264.7 s
Sep 5, 20264.7 s
Sep 12, 20264.7 s
Sep 19, 20264.8 s
Sep 26, 20264.7 s
Oct 3, 20264.6 s
Oct 10, 20264.5 s
Oct 17, 20264.3 s
Oct 24, 20264.3 s
Oct 31, 20264.3 s
Nov 7, 20264.3 s
Nov 14, 20264.4 s
Real-visitor tap response (INP)75th percentile, phones
160 ms118 msMay 30Nov 14124 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026137 ms
Jun 6, 2026128 ms
Jun 13, 2026127 ms
Jun 20, 2026127 ms
Jun 27, 2026131 ms
Jul 4, 2026138 ms
Jul 11, 2026144 ms
Jul 18, 2026151 ms
Jul 25, 2026150 ms
Aug 1, 2026155 ms
Aug 8, 2026154 ms
Aug 15, 2026149 ms
Aug 22, 2026149 ms
Aug 29, 2026146 ms
Sep 5, 2026150 ms
Sep 12, 2026149 ms
Sep 19, 2026145 ms
Sep 26, 2026140 ms
Oct 3, 2026134 ms
Oct 10, 2026129 ms
Oct 17, 2026128 ms
Oct 24, 2026128 ms
Oct 31, 2026124 ms
Nov 7, 2026123 ms
Nov 14, 2026124 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 socialpoint.es (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. socialpoint.es at 0.4 s0.4 s
  2. socialpoint.es at 0.8 s0.8 s
  3. socialpoint.es at 1.1 s1.1 s
  4. socialpoint.es at 1.5 s1.5 s
  5. socialpoint.es at 1.9 s1.9 s
  6. socialpoint.es at 2.3 s2.3 s
  7. socialpoint.es at 2.6 s2.6 s
  8. socialpoint.es at 3.0 s3.0 s

Speed

13 to fix53
  • Use efficient cache lifetimes

    41.9 s · 13.2 MB

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

  • Improve image delivery

    27.1 s · 7.5 MB

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

  • Reduce unused JavaScript

    5.8 s · 1,017 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Optanon, Vimeo and Google Analytics and others), adding 12.1 MB and 237 ms of main-thread time.

  • Amazon Web Services adds 1 ms

    1 ms

    Amazon Web Services costs a phone 1 ms of main-thread work and 11.5 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.

  • Mobile performance score: 53

    53/100

    Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    150 ms · 720 KiB

    About 720 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.

  • Render-blocking requests

    700 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 700 ms.

  • Duplicated JavaScript

    600 ms · 73 KiB

    73 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 600 ms faster on a phone.

  • Legacy JavaScript

    450 ms · 55 KiB

    Polyfills for old browsers add 55 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

  • Document request latency

    504 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Main-thread work: 2.6 s

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

  • Vimeo adds 97 ms

    97 ms

    Vimeo costs a phone 97 ms of main-thread work and 394 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.

  • 7 long tasks on the main thread

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

  • Font display

    100 ms

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

  • 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: 49 ms

    49 ms

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

Core Web Vitals

9 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 LCP: 4.4 s

    4.4 s

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

  • Largest Contentful Paint: 62.0 s

    62.0 s

    Your largest element takes 62.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Game details”.

  • Speed Index: 18.1 s

    18.1 s

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

  • Time to Interactive: 62.9 s

    62.9 s

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

  • First Contentful Paint: 5.3 s

    5.3 s

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

  • Real-user FCP: 2.9 s

    2.9 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • 14 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -7%

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

4 checks passed
  • Real-user INP: 124 ms

    124 ms

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

  • Real-user CLS: 0.04

    0.04

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

  • Total Blocking Time: 180 ms

    180 ms

    Scripts block the page for only 180 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.021

    0.021

    The layout barely moves while loading (CLS 0.021, good is under 0.1).

Images and page weight

5 to fix28
  • Page weight: 15.2 MB in 100 requests

    15.2 MB

    Your homepage downloads 15.2 MB in 100 requests on a phone: images 12.2 MB (36), scripts 2.0 MB (22) and HTML 764 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 8.6 MB together. On a phone connection a single image that size takes seconds.

  • 16 images in older formats

    16 images (10.7 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.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 4 images far larger than shown

    435 KiB

    4 images are downloaded at several times the size a phone draws them, for example life_at_socialpoint_1.jpg at 2,048 px wide, shown at 351 px. Resized copies would save about 435 KiB.

  • About 4.3 g of CO₂ per visit

    4.31 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.31 g of CO₂e: 517.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

5 to fixGoogle 9592
  • <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.

  • 4 images without alt text

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

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

    All page content should be contained by landmarks: 36 elements on the page fail this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • 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 (h2 → h4), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 39 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: 39 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 9270
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (11 characters)

    Your title is only 11 characters: “Socialpoint”. 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.

  • 2 links with vague text

    2 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 incomplete here.

  • 24 internal links, 34 external

    The homepage links to 24 pages on socialpoint.es and 34 external pages.

3 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “Socialpoint is a world-renowned game developer and publisher, specialized in mobile gaming. Join our team and be part o…”.

  • 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.socialpoint.es/sitemap.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.socialpoint.es/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 (700 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix71
  • 10 pages without a title

    /, https://www.socialpoint.es/join-us, https://www.socialpoint.es/games, https://www.socialpoint.es/games/dragon-city, https://www.socialpoint.es/games/two-dots and https://www.socialpoint.es/games/monster-legends and 4 others have no <title>, so Google invents the link text in results.

  • 10 pages without a meta description

    /, https://www.socialpoint.es/join-us, https://www.socialpoint.es/games, https://www.socialpoint.es/games/dragon-city, https://www.socialpoint.es/games/two-dots and https://www.socialpoint.es/games/monster-legends and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    /, https://www.socialpoint.es/join-us, https://www.socialpoint.es/games, https://www.socialpoint.es/games/dragon-city, https://www.socialpoint.es/games/two-dots and https://www.socialpoint.es/games/monster-legends and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 internal pages checked

    We fetched 10 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 10 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.

Best practices

4 to fixGoogle 5086
  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 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 “Failed to load resource: the server responded with a status of 404 ()”.

  • 2 distorted images

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    10 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix60
  • 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: “0 M+ downloads”. 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 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 575 words of copy

    The homepage carries about 575 words of visible text.

2 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Join us”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Analytics (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.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies, 3 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: 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 socialpoint.es, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Gatsby
Analytics
Google Analytics
Hosting
AWS

Hiring

Hiring
9 open roles
Teams
Zynga Mobile Studios (7), Zynga Technology (2)
Job board
greenhouse

Company

Employees
300
Founded
2008
Headquarters
Barcelona

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on socialpoint.es, including 22 speed issues, 6 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

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