Tools & Wizards About Us
stoller.com.br screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

stoller.com.br

Stoller | Soluções em Fisiologia, Nutrição Vegetal e Agricultura

Page Load Speed

3.9 sec in total

First Response

204 ms

Resources Loaded

3.2 sec

Page Rendered

497 ms

stoller.com.br screenshot

About Website

Welcome to stoller.com.br homepage info - get ready to check Stoller best content for Brazil right away, or after learning these important things about stoller.com.br

Stoller: Soluções inovadoras para agricultura. Descubra como impulsionamos o crescimento das suas culturas.

Visit stoller.com.br

Key Findings

We analyzed Stoller.com.br page load time and found that the first response time was 204 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

stoller.com.br performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value9,250 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value62.9 s

0/100

10%

Network Requests Diagram

stoller.com.br

204 ms

www.stoller.com.br

597 ms

css

69 ms

main.css

210 ms

main2.css

96 ms

Our browser made a total of 253 requests to load all elements on the main page. We found that 93% of them (236 requests) were addressed to the original Stoller.com.br, 2% (5 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (597 ms) belongs to the original domain Stoller.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (21%)

Content Size

8.2 MB

After Optimization

6.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stoller.com.br main page is 8.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. Images take 6.4 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 318.0 kB

  • Original 362.6 kB
  • After minification 247.3 kB
  • After compression 44.7 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 115.3 kB, which is 32% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 318.0 kB or 88% of the original size.

Image Optimization

-5%

Potential reduce by 321.1 kB

  • Original 6.4 MB
  • After minification 6.1 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Stoller images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 831.6 kB

  • Original 1.1 MB
  • After minification 826.0 kB
  • After compression 245.6 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 831.6 kB or 77% of the original size.

CSS Optimization

-85%

Potential reduce by 294.6 kB

  • Original 348.3 kB
  • After minification 320.2 kB
  • After compression 53.7 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Stoller.com.br needs all CSS files to be minified and compressed as it can save up to 294.6 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (8%)

Requests Now

246

After Optimization

226

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 246 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stoller. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

stoller.com.br

stoller.com.br

204 ms

www.stoller.com.br

www.stoller.com.br

597 ms

css

css

69 ms

main.css

main.css

210 ms

main2.css

main2.css

96 ms

modernizr.js

modernizr.js

174 ms

slick.css

slick.css

90 ms

tm38742.js

tm38742.js

72 ms

jquery.js

jquery.js

157 ms

jquery-ui.min.js

jquery-ui.min.js

419 ms

slick.min.js

slick.min.js

154 ms

scrollReveal.js

scrollReveal.js

151 ms

culturas.js

culturas.js

214 ms

necessidades.js

necessidades.js

214 ms

main.js

main.js

261 ms

necessidades-builder.js

necessidades-builder.js

246 ms

analytics.js

analytics.js

31 ms

usr

usr

122 ms

banner-institucional.jpg

banner-institucional.jpg

281 ms

mapa-vetor.png

mapa-vetor.png

138 ms

gtm.js

gtm.js

119 ms

6bnJdBOqV_A

6bnJdBOqV_A

140 ms

stoller_sprite.png

stoller_sprite.png

101 ms

stoller_setas.png

stoller_setas.png

136 ms

home-cultura-nav.png

home-cultura-nav.png

120 ms

home-especialista_bg.png

home-especialista_bg.png

297 ms

home-footer.jpg

home-footer.jpg

558 ms

collect

collect

38 ms

Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf

Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf

51 ms

b9QBgL0iMZfDSpmcXcE8nL3QFSXBldIn45k5A7iXhnc.ttf

b9QBgL0iMZfDSpmcXcE8nL3QFSXBldIn45k5A7iXhnc.ttf

64 ms

b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf

b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf

70 ms

req

req

161 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

46 ms

www-embed-player.js

www-embed-player.js

81 ms

Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js

Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js

178 ms

ad_status.js

ad_status.js

188 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

133 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

133 ms

thumb.png

thumb.png

77 ms

thumb.png

thumb.png

75 ms

thumb.png

thumb.png

125 ms

thumb.png

thumb.png

120 ms

thumb.png

thumb.png

120 ms

thumb.png

thumb.png

118 ms

thumb.png

thumb.png

114 ms

thumb.png

thumb.png

152 ms

thumb.png

thumb.png

173 ms

thumb.png

thumb.png

168 ms

1.png

1.png

241 ms

2.png

2.png

294 ms

3.png

3.png

194 ms

4.png

4.png

222 ms

1.png

1.png

211 ms

1.png

1.png

214 ms

2.png

2.png

237 ms

3.png

3.png

255 ms

4.png

4.png

257 ms

1.png

1.png

258 ms

2.png

2.png

282 ms

3.png

3.png

284 ms

1.png

1.png

298 ms

2.png

2.png

302 ms

1.png

1.png

297 ms

2.png

2.png

326 ms

3.png

3.png

365 ms

4.png

4.png

411 ms

1.png

1.png

332 ms

2.png

2.png

340 ms

3.png

3.png

342 ms

1.png

1.png

373 ms

2.png

2.png

369 ms

3.png

3.png

382 ms

4.png

4.png

395 ms

5.png

5.png

344 ms

1.png

1.png

344 ms

2.png

2.png

313 ms

1.png

1.png

319 ms

2.png

2.png

322 ms

1.png

1.png

381 ms

2.png

2.png

384 ms

3.png

3.png

337 ms

4.png

4.png

319 ms

5.png

5.png

351 ms

1.png

1.png

312 ms

2.png

2.png

321 ms

1.png

1.png

317 ms

2.png

2.png

308 ms

1.png

1.png

321 ms

2.png

2.png

309 ms

3.png

3.png

317 ms

1.png

1.png

306 ms

2.png

2.png

302 ms

1.png

1.png

314 ms

1.png

1.png

341 ms

2.png

2.png

343 ms

3.png

3.png

310 ms

4.png

4.png

300 ms

5.png

5.png

342 ms

1.png

1.png

313 ms

2.png

2.png

306 ms

1.png

1.png

309 ms

2.png

2.png

319 ms

3.png

3.png

321 ms

1.png

1.png

307 ms

2.png

2.png

300 ms

1.png

1.png

310 ms

2.png

2.png

299 ms

3.png

3.png

306 ms

1.png

1.png

298 ms

2.png

2.png

296 ms

1.png

1.png

342 ms

2.png

2.png

349 ms

3.png

3.png

303 ms

4.png

4.png

354 ms

1.png

1.png

281 ms

2.png

2.png

274 ms

3.png

3.png

310 ms

1.png

1.png

290 ms

2.png

2.png

302 ms

1.png

1.png

291 ms

2.png

2.png

300 ms

1.png

1.png

303 ms

2.png

2.png

310 ms

3.png

3.png

300 ms

4.png

4.png

301 ms

1.png

1.png

335 ms

2.png

2.png

342 ms

3.png

3.png

302 ms

4.png

4.png

346 ms

1.png

1.png

288 ms

1.png

1.png

293 ms

2.png

2.png

282 ms

3.png

3.png

309 ms

4.png

4.png

320 ms

1.png

1.png

311 ms

2.png

2.png

296 ms

3.png

3.png

304 ms

4.png

4.png

314 ms

5.png

5.png

324 ms

1.png

1.png

309 ms

2.png

2.png

330 ms

thumb.png

thumb.png

321 ms

thumb.png

thumb.png

305 ms

thumb.png

thumb.png

320 ms

thumb.png

thumb.png

309 ms

thumb.png

thumb.png

329 ms

1.png

1.png

343 ms

2.png

2.png

339 ms

3.png

3.png

335 ms

4.png

4.png

300 ms

1.png

1.png

299 ms

2.png

2.png

299 ms

1.png

1.png

306 ms

1.png

1.png

324 ms

2.png

2.png

320 ms

3.png

3.png

327 ms

1.png

1.png

315 ms

1.png

1.png

315 ms

2.png

2.png

299 ms

3.png

3.png

369 ms

4.png

4.png

358 ms

1.png

1.png

317 ms

2.png

2.png

291 ms

3.png

3.png

282 ms

1.png

1.png

290 ms

2.png

2.png

314 ms

3.png

3.png

319 ms

1.png

1.png

306 ms

2.png

2.png

295 ms

3.png

3.png

312 ms

1.png

1.png

306 ms

2.png

2.png

301 ms

3.png

3.png

324 ms

1.png

1.png

295 ms

2.png

2.png

293 ms

3.png

3.png

294 ms

4.png

4.png

302 ms

1.png

1.png

297 ms

1.png

1.png

309 ms

2.png

2.png

301 ms

3.png

3.png

291 ms

1.png

1.png

284 ms

1.png

1.png

284 ms

2.png

2.png

273 ms

1.png

1.png

284 ms

2.png

2.png

278 ms

3.png

3.png

277 ms

4.png

4.png

268 ms

1.png

1.png

288 ms

2.png

2.png

273 ms

1.png

1.png

273 ms

2.png

2.png

277 ms

3.png

3.png

278 ms

1.png

1.png

272 ms

2.png

2.png

292 ms

1.png

1.png

260 ms

1.png

1.png

258 ms

2.png

2.png

271 ms

3.png

3.png

271 ms

4.png

4.png

251 ms

1.png

1.png

262 ms

2.png

2.png

264 ms

3.png

3.png

255 ms

1.png

1.png

273 ms

2.png

2.png

272 ms

3.png

3.png

254 ms

1.png

1.png

265 ms

2.png

2.png

261 ms

3.png

3.png

247 ms

1.png

1.png

269 ms

2.png

2.png

268 ms

1.png

1.png

261 ms

2.png

2.png

254 ms

3.png

3.png

261 ms

4.png

4.png

247 ms

1.png

1.png

269 ms

2.png

2.png

268 ms

3.png

3.png

268 ms

1.png

1.png

246 ms

2.png

2.png

260 ms

3.png

3.png

247 ms

4.png

4.png

268 ms

5.png

5.png

261 ms

1.png

1.png

268 ms

2.png

2.png

253 ms

3.png

3.png

258 ms

1.png

1.png

255 ms

2.png

2.png

252 ms

1.png

1.png

266 ms

2.png

2.png

266 ms

3.png

3.png

254 ms

4.png

4.png

257 ms

1.png

1.png

300 ms

1.png

1.png

275 ms

1.png

1.png

308 ms

1.png

1.png

310 ms

1.png

1.png

252 ms

2.png

2.png

259 ms

3.png

3.png

298 ms

4.png

4.png

267 ms

1.png

1.png

278 ms

1.png

1.png

275 ms

2.png

2.png

294 ms

3.png

3.png

285 ms

4.png

4.png

289 ms

1.png

1.png

278 ms

2.png

2.png

281 ms

3.png

3.png

276 ms

4.png

4.png

288 ms

5.png

5.png

295 ms

1.png

1.png

292 ms

2.png

2.png

279 ms

culturas-reflexo.png

culturas-reflexo.png

279 ms

Accessibility Review

stoller.com.br accessibility score

79

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Form elements do not have associated labels

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

stoller.com.br best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

stoller.com.br SEO score

82

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stoller.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Stoller.com.br main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

stoller.com.br

Open Graph description is not detected on the main page of Stoller. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: