Tools & Wizards About Us
hortofolgosa.com screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

hortofolgosa.com

Homepage | Horto de Folgosa

Page Load Speed

6.2 sec in total

First Response

620 ms

Resources Loaded

5.3 sec

Page Rendered

313 ms

hortofolgosa.com screenshot

About Website

Welcome to hortofolgosa.com homepage info - get ready to check Horto Folgosa best content for Portugal right away, or after learning these important things about hortofolgosa.com

O Horto Folgosa está localizado na Maia. Especializamo-nos no fornecimento de plantas ornamentais para Profissionais.

Visit hortofolgosa.com

Key Findings

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

Performance Metrics

hortofolgosa.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value420 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0.019

100/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

www.hortofolgosa.com

620 ms

gtm.js

88 ms

bootstrap.min.css

62 ms

aos.css

74 ms

slick.css

83 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Hortofolgosa.com, 41% (13 requests) were made to Static.lvengine.net and 19% (6 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source Static.lvengine.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 517.5 kB (7%)

Content Size

7.8 MB

After Optimization

7.2 MB

  • HTML
  • Images

In fact, the total size of Hortofolgosa.com main page is 7.8 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. 55% of websites need less resources to load. Images take 7.7 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 16.2 kB

  • Original 21.9 kB
  • After minification 20.4 kB
  • After compression 5.8 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 16.2 kB or 74% of the original size.

Image Optimization

-6%

Potential reduce by 501.4 kB

  • Original 7.7 MB
  • After minification 7.2 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. Horto Folgosa images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 12 (46%)

Requests Now

26

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.hortofolgosa.com

www.hortofolgosa.com

620 ms

gtm.js

gtm.js

88 ms

bootstrap.min.css

bootstrap.min.css

62 ms

aos.css

aos.css

74 ms

slick.css

slick.css

83 ms

all.min.css

all.min.css

52 ms

css2

css2

76 ms

site.css

site.css

586 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

113 ms

jquery.cookie.min.js

jquery.cookie.min.js

113 ms

aos.js

aos.js

79 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

112 ms

lazyload.min.js

lazyload.min.js

79 ms

slick.min.js

slick.min.js

110 ms

site.js

site.js

725 ms

536

536

2246 ms

logo-horto-folgosa.png

logo-horto-folgosa.png

220 ms

20161006_1527422.jpg

20161006_1527422.jpg

3638 ms

IMG-20151111-WA0001.jpg

IMG-20151111-WA0001.jpg

1085 ms

IMG-20161102-WA0002.jpg

IMG-20161102-WA0002.jpg

1057 ms

FB_IMG_1664469709359.jpg

FB_IMG_1664469709359.jpg

1104 ms

proteas.jpg

proteas.jpg

594 ms

home_plants.jpg

home_plants.jpg

597 ms

FB_IMG_1664469692640.jpg

FB_IMG_1664469692640.jpg

1146 ms

20220417_164743.jpg

20220417_164743.jpg

1152 ms

IMG-20161017-WA0028.jpg

IMG-20161017-WA0028.jpg

1494 ms

pme.png

pme.png

1194 ms

4iCv6KVjbNBYlgoCjC3TtA.woff

4iCv6KVjbNBYlgoCjC3TtA.woff

33 ms

4iCv6KVjbNBYlgoCxCvTtA.woff

4iCv6KVjbNBYlgoCxCvTtA.woff

67 ms

fa-solid-900.ttf

fa-solid-900.ttf

32 ms

fa-regular-400.ttf

fa-regular-400.ttf

20 ms

fa-brands-400.ttf

fa-brands-400.ttf

66 ms

Accessibility Review

hortofolgosa.com 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

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

hortofolgosa.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

hortofolgosa.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

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 Hortofolgosa.com 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 Hortofolgosa.com 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

hortofolgosa.com

Open Graph data is detected on the main page of Horto Folgosa. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: