Website review, no card needed
99999.hu website review
Visit site (opens in a new tab)Reviewed 25 October 202645 issues · 90 checks
This review found 45 issues worth fixing on 99999.hu, 21 of them high impact, across 90 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
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jun 6, 2026 | 6.8 s |
| Jun 27, 2026 | 6.6 s |
| Jul 11, 2026 | 5.7 s |
| Jul 18, 2026 | 5.8 s |
| Jul 25, 2026 | 6.0 s |
| Aug 1, 2026 | 6.1 s |
| Aug 8, 2026 | 6.2 s |
| Aug 15, 2026 | 6.1 s |
| Aug 22, 2026 | 6.2 s |
| Aug 29, 2026 | 6.1 s |
| Sep 5, 2026 | 6.5 s |
| Sep 12, 2026 | 6.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jul 25, 2026 | 249 ms |
| Aug 1, 2026 | 274 ms |
| Aug 8, 2026 | 274 ms |
| Aug 15, 2026 | 267 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
Speed
Use efficient cache lifetimes
19.1 s · 8.8 MB174 files are served with short cache lifetimes, so returning visitors download them again (8.8 MB).
Reduce unused JavaScript
6.6 s · 2.8 MBAbout 2.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.6 s faster on a phone.
Render-blocking requests
8.5 s54 files block the first paint until they finish downloading. Deferring or inlining them could save about 8.5 s.
Reduce unused CSS
3.6 s · 689 KiBAbout 689 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.6 s faster on a phone.
Improve image delivery
1.5 s · 1.2 MB19 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.
Mobile performance score: 47
47/100Your mobile performance score is 47 (desktop: 62). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Font display
950 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 950 ms).
6 third-party services on the page
6 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.5 MB and 739 ms of main-thread time.
Google CDN adds 358 ms
358 msGoogle CDN costs a phone 358 ms of main-thread work and 731 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.
Google Tag Manager adds 347 ms
347 msGoogle Tag Manager costs a phone 347 ms of main-thread work and 563 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.
Minify CSS
300 ms · 35 KiB35 KiB could be saved by minifying CSS.
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
250 ms · 27 KiBPolyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
Document request latency
203 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Minify JavaScript
150 ms · 7 KiB7 KiB could be saved by minifying JavaScript.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 152 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.
1 checks passed
Server response: 459 ms
459 msYour server sent the HTML in 459 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 FCP: 5.3 s
5.3 sReal visitors see the first content after 5.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.4 s
2.4 sReal visitors wait 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 11.0 s
11.0 sThe first text or image appears after 11.0 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 27.8 s
27.8 sYour largest element takes 27.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “hero-99999”.
Time to Interactive: 50.6 s
50.6 sThe page becomes fully interactive after 50.6 s. Good is under 3.8 s.
Speed Index: 14.3 s
14.3 sVisually, the page fills in at 14.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 353 ms
353 msScripts block taps and scrolling for 353 ms in total while the page loads. Good is under 200 ms.
16 images without width and height
16 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-17, real Chrome visitors' tap response (inp) went from 249 ms to 267 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 6.8 s to 6.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 10.9 MB in 196 requests
10.9 MBYour homepage downloads 10.9 MB in 196 requests on a phone: scripts 5.4 MB (93), images 3.6 MB (37) and stylesheets 891 KiB (52). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
foldgomb-768x768.png weighs 994 KiB. On a phone connection a single image that size takes seconds.
3 images in older formats
3 images (1.1 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.
1 image far larger than shown
33 KiB1 image is downloaded at several times the size a phone draws it, for example logo-colored-99999-768x493.png at 390 px wide, shown at 80 px. Resized copies would save about 33 KiB.
5 images below the first screen load straight away
5 images further down the page (116 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.1 g of CO₂ per visit
3.10 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.10 g of CO₂e: 372.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 links without text
2 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 (h4 → h6, h2 → h5 and h1 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 26 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (17 characters)
Your title is only 17 characters: “99999 Informatika”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (279 characters)
Your meta description is 279 characters; Google truncates after about 160, so the end of your pitch is cut.
42 internal links, 5 external
The homepage links to 42 pages on 99999.hu and 5 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Kérj ajánlatot tőlünk!”.
Canonical URL set
The canonical URL is https://99999.hu/.
Structured data in place
Structured data found: BreadcrumbList, 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://99999.hu/sitemap.xml.
AI search readiness
4 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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (669 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://99999.hu/llms.txt (70 KiB, 253 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://99999.hu/blog and https://99999.hu/en all use the title “Blog - 99999”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://99999.hu/blog and https://99999.hu/en use the same meta description. A description written for each page earns more clicks.
8 pages slow to respond
https://99999.hu/rolunk, https://99999.hu/vezetoink, https://99999.hu/fenntarthatosag, https://99999.hu/uzletagaink, https://99999.hu/gyengaramu-rendszerek and https://99999.hu/hybrid-it and 2 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
5 broken images
5 images failed to load on a phone, for example https://99999.hu/wp-content/uploads/2022/03/foldgomb-768x768.png.
13 small tap targets
13 of 24 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_HTTP2_PROTOCOL_ERROR”.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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 447 words of copy
The homepage carries about 447 words of visible text.
4 checks passed
1 short form
A short form (5 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 3 phone links and 2 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
10 cookies set on arrival
10Opening the homepage sets 10 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.
8 other companies contacted
Loading the homepage contacts 8 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 99999.hu, 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
- React
- Analytics
- Google Analytics
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 99999.hu, including 21 speed issues, 2 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.