Website review, no card needed
werk-schott.com.br website review
Visit site (opens in a new tab)Reviewed 24 October 202646 issues · 85 checks
This review found 46 issues worth fixing on werk-schott.com.br, 16 of them high impact, across 85 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.3 s |
| May 9, 2026 | 2.3 s |
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 168 ms |
| May 9, 2026 | 159 ms |
| May 16, 2026 | 149 ms |
| May 23, 2026 | 149 ms |
| May 30, 2026 | 141 ms |
| Jun 6, 2026 | 141 ms |
| Jun 13, 2026 | 136 ms |
| Jun 20, 2026 | 142 ms |
| Jun 27, 2026 | 149 ms |
| Jul 4, 2026 | 155 ms |
| Jul 11, 2026 | 162 ms |
| Jul 18, 2026 | 148 ms |
| Jul 25, 2026 | 150 ms |
| Aug 1, 2026 | 158 ms |
| Aug 8, 2026 | 161 ms |
| Aug 15, 2026 | 185 ms |
| Aug 22, 2026 | 170 ms |
| Aug 29, 2026 | 169 ms |
| Sep 5, 2026 | 179 ms |
| Sep 12, 2026 | 180 ms |
| Sep 19, 2026 | 207 ms |
| Sep 26, 2026 | 209 ms |
| Oct 3, 2026 | 191 ms |
| Oct 10, 2026 | 189 ms |
| Oct 17, 2026 | 180 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
How it loaded on a phone
0.9 s
1.8 s
2.6 s
3.5 s
4.4 s
5.3 s
6.1 s
7.0 s
Speed
Use efficient cache lifetimes
2.3 s · 2.1 MB85 files are served with short cache lifetimes, so returning visitors download them again (2.1 MB).
Render-blocking requests
2.9 s30 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.9 s.
Improve image delivery
600 ms · 1.2 MB5 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 600 ms faster on a phone.
Mobile performance score: 57
57/100Your mobile performance score is 57 (desktop: 65). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and RD Station and others), adding 1.2 MB and 730 ms of main-thread time.
Reduce unused JavaScript
150 ms · 416 KiBAbout 416 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Google Tag Manager adds 421 ms
421 msGoogle Tag Manager costs a phone 421 ms of main-thread work and 723 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 186 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 3 KiB3 KiB could be saved by minifying CSS.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
13 KiBAbout 13 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
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 JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 773 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 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: 3.5 s
3.5 sReal visitors see the first content after 3.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.0 s
3.0 sReal visitors wait 3.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 15.7 s
15.7 sThe page becomes fully interactive after 15.7 s. Good is under 3.8 s.
Largest Contentful Paint: 6.8 s
6.8 sYour largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Inovação que conecta e transforma. 40 anos movendo a indúst…”. Most of its time is resource load delay (4.1 s).
Speed Index: 8.5 s
8.5 sVisually, the page fills in at 8.5 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.8 s
3.8 sReal visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 238 ms
238 msReal visitors wait 238 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 29% slower for real visitors
+29%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.3 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Total Blocking Time: 252 ms
252 msScripts block taps and scrolling for 252 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.1
0.1The layout shifts by 0.1 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 168 ms to 180 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Images and page weight
1 image over 500 KB
bannerPost.png weighs 967 KiB. On a phone connection a single image that size takes seconds.
3 images far larger than shown
885 KiB3 images are downloaded at several times the size a phone draws them, for example bannerPost.png at 1,800 px wide, shown at 335 px. Resized copies would save about 885 KiB.
Page weight: 3.0 MB in 127 requests
3.0 MBYour homepage downloads 3.0 MB in 127 requests on a phone: images 1.5 MB (15), scripts 1.3 MB (53) and other files 93 KiB (14). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (1.3 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.
2 images below the first screen load straight away
2 images further down the page (158 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.86 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.86 g of CO₂e: 103.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must contain particular children (4 elements)
Certain ARIA roles must contain particular children: 4 elements on the page fail this check, rated critical by axe-core.
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 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.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (4 elements).
2 checks passed
Every image has alt text
All 6 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 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 6 failed. 2 mores 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 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: “Werk Schott”. 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 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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
42 internal links, 11 external
The homepage links to 42 pages on werk-schott.com.br and 11 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://werk-schott.com.br/.
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://werk-schott.com.br/wp-sitemap.xml.
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://werk-schott.com.br/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 (322 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a meta description
https://werk-schott.com.br/produtos, https://werk-schott.com.br/produtos/lancamentos, https://werk-schott.com.br/produtos/valvulas, https://werk-schott.com.br/produtos/tubos_conexoes, https://werk-schott.com.br/produtos/cilindros_pneumaticos and https://werk-schott.com.br/produtos/elementos_automacao and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://werk-schott.com.br/produtos, https://werk-schott.com.br/noticias, https://werk-schott.com.br/sobre-nos, https://werk-schott.com.br/fale-conosco and https://werk-schott.com.br/trabalhe-conosco have no <h1> headline, so visitors and search engines get no clear main topic.
8 pages slow to respond
https://werk-schott.com.br/produtos, https://werk-schott.com.br/produtos/lancamentos, https://werk-schott.com.br/produtos/valvulas, https://werk-schott.com.br/produtos/tubos_conexoes, https://werk-schott.com.br/produtos/cilindros_pneumaticos and https://werk-schott.com.br/produtos/elementos_automacao 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 (of 17 found) and read each the way a search engine does.
5 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.
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 15 pages that loaded have a <title>.
Best practices
10 small tap targets
10 of 18 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
3 low-resolution images
3 images are served at too low a resolution for sharp phone screens.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
A 9-field form
Your longest form asks for 9 fields (0 required). Every extra field lowers completion.
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 246 words
The homepage has only about 246 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.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Start search”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
20 other companies contacted
Loading the homepage contacts 20 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 werk-schott.com.br, 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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on werk-schott.com.br, including 19 speed issues, 5 SEO issues and 5 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.