Website review, no card needed
soluqrh.com website review
Visit site (opens in a new tab)Reviewed 10 November 202631 issues · 75 checks
This review found 31 issues worth fixing on soluqrh.com, 7 of them high impact, across 75 checks. The most urgent: render-blocking requests. 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
80BClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
1.1 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 87
87/100Your mobile performance score is 87. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
250 ms · 355 KiB34 files are served with short cache lifetimes, so returning visitors download them again (355 KiB).
Google Tag Manager adds 147 ms
147 msGoogle Tag Manager costs a phone 147 ms of main-thread work and 306 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.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, FontAwesome CDN and Cloudflare CDN and others), adding 376 KiB and 155 ms of main-thread time.
Reduce unused CSS
150 ms · 35 KiBAbout 35 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.
Improve image delivery
166 KiB7 images could be 166 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
164 KiBAbout 164 KiB of JavaScript is downloaded but never used on this page.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 113 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.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 0.5 s
A phone's processor spends 0.5 s on main-thread work while loading, 209 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 8.7 s
8.7 sVisually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 5.5 s
5.5 sThe page becomes fully interactive after 5.5 s. Good is under 3.8 s.
20 images without width and height
20 images have no width and height attributes, so the layout jumps as each one loads.
Largest Contentful Paint: 2.8 s
2.8 sYour largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A SoluQ RH conecta o recrutamento e seleção, a admissão, in…”. Most of its time is element render delay (5.6 s).
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.
3 checks passed
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Total Blocking Time: 32 ms
32 msScripts block the page for only 32 ms while loading. Good is under 200 ms.
Images and page weight
1 image far larger than shown
46 KiB1 image is downloaded at several times the size a phone draws it, for example selo-startup-acelerada-inovativa.png at 354 px wide, shown at 70 px. Resized copies would save about 46 KiB.
2 images in older formats
2 images (105 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.
4 images below the first screen load straight away
4 images further down the page (151 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.2 g of CO₂ per visit
0.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.20 g of CO₂e: 24.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 731 KiB in 45 requests
731 KiBYour homepage downloads 731 KiB in 45 requests on a phone: scripts 405 KiB (13), images 222 KiB (19) and stylesheets 41 KiB (6). That is a lean page.
Accessibility
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.
<html> element must have a valid value for the lang attribute (1 element)
<html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 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.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Page language is “pt_BR”
The page declares lang=“pt_BR”, which is not a usable language code, so screen readers and translation tools guess.
2 checks passed
Every image has alt text
All 21 images in the HTML carry an alt attribute.
28 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 33 WCAG 2.2 A/AA and best-practice rules on the phone render: 28 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
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 XML sitemap
No XML sitemap at https://soluqrh.com/sitemap.xml, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
22 internal links, 9 external
The homepage links to 22 pages on soluqrh.com and 9 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Profissionalize as contratações da sua empresa”.
Title: 41 characters
Your title is a healthy 41 characters: “SoluQ RH - Plataforma para R&S e Admissão”.
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.
AI search readiness
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://soluqrh.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.
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 (203 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
/ and https://soluqrh.com/plataforma all use the title “SoluQ RH - Plataforma para R&S e Admissão”. Search engines can't tell which page to show for a search, so each competes with the others.
12 pages without a meta description
https://soluqrh.com/plataforma, https://soluqrh.com/planos, https://soluqrh.com/vagas, https://soluqrh.com/trabalheconosco/docato, https://soluqrh.com/trabalheconosco/marhia and https://soluqrh.com/trabalheconosco/kirstenconsultoria and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
9 pages without an H1
https://soluqrh.com/vagas, https://soluqrh.com/trabalheconosco/docato, https://soluqrh.com/trabalheconosco/marhia, https://soluqrh.com/trabalheconosco/kirstenconsultoria, https://soluqrh.com/trabalheconosco/wise and https://soluqrh.com/trabalheconosco/futurerh and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://soluqrh.com/trabalheconosco/wise 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.
3 pages slow to respond
https://soluqrh.com/planos, https://soluqrh.com/vagas and https://soluqrh.com/trabalheconosco/docato took over 3 s to send their HTML from our server.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 13 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.
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
9 small tap targets
9 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 203 words
The homepage has only about 203 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 1 customer or partner logo and 1 trust badge.
Analytics in place
Analytics detected: Google Analytics.
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.
2 cookies set on arrival
2Opening the homepage sets 2 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 soluqrh.com, 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
- Hosting
- Immedion, LLC
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on soluqrh.com, including 8 speed issues, 4 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.