Website review, no card needed

personal.com.py logo

personal.com.py website review

Visit site (opens in a new tab)Reviewed 26 October 202656 issues · 91 checks

This review found 56 issues worth fixing on personal.com.py, 25 of them high impact, across 91 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.7 s2.0 sMay 9Oct 242.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.6 s
May 16, 20262.5 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.5 s
Aug 8, 20262.3 s
Aug 15, 20262.2 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.2 s
Sep 12, 20262.3 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Oct 24, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
267 ms188 msMay 9Oct 24229 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026233 ms
May 16, 2026238 ms
May 23, 2026241 ms
May 30, 2026253 ms
Jun 6, 2026258 ms
Jun 13, 2026248 ms
Jun 20, 2026245 ms
Jun 27, 2026230 ms
Jul 4, 2026229 ms
Jul 11, 2026222 ms
Jul 18, 2026214 ms
Jul 25, 2026213 ms
Aug 1, 2026213 ms
Aug 8, 2026205 ms
Aug 15, 2026199 ms
Aug 22, 2026197 ms
Aug 29, 2026205 ms
Sep 5, 2026211 ms
Sep 12, 2026219 ms
Sep 19, 2026223 ms
Sep 26, 2026220 ms
Oct 3, 2026221 ms
Oct 10, 2026228 ms
Oct 17, 2026230 ms
Oct 24, 2026229 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 personal.com.py (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. personal.com.py at 1.0 s1.0 s
  2. personal.com.py at 2.0 s2.0 s
  3. personal.com.py at 3.0 s3.0 s
  4. personal.com.py at 4.0 s4.0 s
  5. personal.com.py at 5.0 s5.0 s
  6. personal.com.py at 6.0 s6.0 s
  7. personal.com.py at 7.0 s7.0 s
  8. personal.com.py at 8.0 s8.0 s

Speed

12 to fix13
  • Use efficient cache lifetimes

    5.3 s · 8.5 MB

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

  • Render-blocking requests

    3.9 s

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

  • Reduce unused JavaScript

    2.5 s · 808 KiB

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

  • Font display

    2.6 s

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

  • Google Tag Manager adds 1.4 s

    1.4 s

    Google Tag Manager costs a phone 1.4 s of main-thread work and 1.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Reduce unused CSS

    1.1 s · 130 KiB

    About 130 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 13

    13/100

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

  • Main-thread work: 4.6 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, TikTok and Facebook and others), adding 1.9 MB and 2.0 s of main-thread time.

  • Improve image delivery

    1.6 MB

    9 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify CSS

    450 ms · 5 KiB

    5 KiB could be saved by minifying CSS.

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    21 KiB

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

  • Minify JavaScript

    10 KiB

    10 KiB could be saved by minifying JavaScript.

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

    2 ms

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

Core Web Vitals

13 to fix0
  • 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.55

    0.55

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

  • Cumulative Layout Shift: 1.564

    1.564

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

  • Largest Contentful Paint: 16.1 s

    16.1 s

    Your largest element takes 16.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Autoactiva tu chip Personal”.

  • Time to Interactive: 51.1 s

    51.1 s

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

  • Speed Index: 14.8 s

    14.8 s

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

  • Total Blocking Time: 1.0 s

    1.0 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Real-user INP: 231 ms

    231 ms

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 836 ms

    836 ms

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

  • 40 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -3%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

Images and page weight

5 to fix18
  • Page weight: 12.4 MB in 187 requests

    12.4 MB

    Your homepage downloads 12.4 MB in 187 requests on a phone: images 9.4 MB (75), scripts 2.0 MB (43) and fonts 535 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 9 images over 500 KB

    9 images weigh 7.5 MB together. On a phone connection a single image that size takes seconds.

  • 5 images far larger than shown

    559 KiB

    5 images are downloaded at several times the size a phone draws them, for example pay-funcionalidades.png at 1,080 px wide, shown at 330 px. Resized copies would save about 559 KiB.

  • 27 images in older formats

    27 images (9.2 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.

  • 11 images below the first screen load straight away

    11 images further down the page (5.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.5 g of CO₂ per visit

    3.52 g

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

Accessibility

6 to fixGoogle 7688
  • 12 text elements with low contrast

    12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 10 images without alt text

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

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

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

  • 5 links without text

    5 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 skip levels

    Headings skip levels (h3 → h5, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 28 automated accessibility rules passed

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

SEO

5 to fixGoogle 8376
  • No H1 headline

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

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

  • Meta description is long (185 characters)

    Your meta description is 185 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 4 links with vague text

    4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 25 internal links, 19 external

    The homepage links to 25 pages on personal.com.py and 19 external pages.

4 checks passed
  • Title: 62 characters

    Your title is a healthy 62 characters: “Personal Paraguay | Internet Fibra + Flow | Planes | Celulares”.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://personal.com.py/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://personal.com.py/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 (570 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix76
  • 6 pages share 3 titles

    https://personal.com.py/flow and https://personal.com.py/flow/index.html all use the title “Flow | Personal Paraguay”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://personal.com.py/mi-personal, https://personal.com.py/smarthome/index.html, https://personal.com.py/smarthome, https://personal.com.py/personal-empresas and https://personal.com.py/mi-personal/index.html have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://personal.com.py/flow and https://personal.com.py/flow/index.html use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://personal.com.py/flow, whose canonical is https://personal.com.py/flow/index.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 6 pages without an H1

    https://personal.com.py/flow, https://personal.com.py/mi-personal, https://personal.com.py/smarthome/index.html, https://personal.com.py/flow/index.html, https://personal.com.py/smarthome and https://personal.com.py/mi-personal/index.html have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://personal.com.py/packs/packs-ilimitados.html 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.

  • 1 page slow to respond

    https://personal.com.py/smarthome/index.html took over 3 s to send its HTML from our server.

  • 11 internal pages checked

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

3 checks passed
  • Linked pages load

    All 11 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

4 to fixGoogle 4686
  • 3 third-party cookies

    3 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.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

  • 3 distorted images

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

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    21 of 22 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix30
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 598 words of copy

    The homepage carries about 598 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 10 trackers load before any consent

    10

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 5 mores (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.

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies (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.

  • 45 other companies contacted

    Loading the homepage contacts 45 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 personal.com.py, 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 Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Nucleo S.A.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 56 issues on personal.com.py, including 25 speed issues, 5 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

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