Tools & Wizards About Us
grow.pe screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

grow.pe

Grow - AI Marketing Agency

Page Load Speed

5.2 sec in total

First Response

51 ms

Resources Loaded

4.9 sec

Page Rendered

244 ms

grow.pe screenshot

About Website

Click here to check amazing Grow content. Otherwise, check out these important facts you probably never knew about grow.pe

We drive your business growth with digital marketing strategies powered by Artificial Intelligence.

Visit grow.pe

Key Findings

We analyzed Grow.pe page load time and found that the first response time was 51 ms and then it took 5.1 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

grow.pe performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value17.3 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value5,430 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value19.4 s

2/100

10%

Network Requests Diagram

grow.pe

51 ms

www.grow.pe

2384 ms

fbevents.js

28 ms

1585341161685031.js

828 ms

PG93VCCnmn8

239 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 30% of them (20 requests) were addressed to the original Grow.pe, 42% (28 requests) were made to Fonts.gstatic.com and 18% (12 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Grow.pe.

Page Optimization Overview & Recommendations

Page size can be reduced by 350.8 kB (16%)

Content Size

2.2 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Grow.pe main page is 2.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 167.1 kB

  • Original 197.5 kB
  • After minification 194.5 kB
  • After compression 30.4 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 167.1 kB or 85% of the original size.

Image Optimization

-6%

Potential reduce by 96.7 kB

  • Original 1.5 MB
  • After minification 1.4 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. Grow images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 87.0 kB

  • Original 373.3 kB
  • After minification 373.3 kB
  • After compression 286.3 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 87.0 kB or 23% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 73.5 kB
  • After minification 73.5 kB
  • After compression 73.5 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. Grow.pe has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (37%)

Requests Now

30

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

grow.pe

grow.pe

51 ms

www.grow.pe

www.grow.pe

2384 ms

fbevents.js

fbevents.js

28 ms

1585341161685031.js

1585341161685031.js

828 ms

PG93VCCnmn8

PG93VCCnmn8

239 ms

hqdefault.jpg

hqdefault.jpg

53 ms

Y68LanwOjgk

Y68LanwOjgk

270 ms

EYjk1EEXy_o

EYjk1EEXy_o

271 ms

jquery.min.js

jquery.min.js

119 ms

jquery-migrate.min.js

jquery-migrate.min.js

104 ms

scripts.min.js

scripts.min.js

131 ms

jquery.fitvids.js

jquery.fitvids.js

94 ms

jquery.mobile.js

jquery.mobile.js

86 ms

common.js

common.js

76 ms

motion-effects.js

motion-effects.js

158 ms

Logo-Grow-azul.png

Logo-Grow-azul.png

157 ms

Grow-Agencia-Digital-Inicio-Web.png

Grow-Agencia-Digital-Inicio-Web.png

312 ms

Agencia-Grow-evento-digital-v2.png

Agencia-Grow-evento-digital-v2.png

308 ms

redes-sociales.png

redes-sociales.png

285 ms

Agencia-Grow-Website.png

Agencia-Grow-Website.png

312 ms

Agencia-Grow-chatbot.png

Agencia-Grow-chatbot.png

312 ms

Zoom-Grow-Diciembre-2021.jpeg

Zoom-Grow-Diciembre-2021.jpeg

286 ms

preloader.gif

preloader.gif

313 ms

Grow-Agencia-Marketing-Brochure-de-Servicios.jpeg

Grow-Agencia-Marketing-Brochure-de-Servicios.jpeg

312 ms

scc-c2.min.js

scc-c2.min.js

6 ms

www-player.css

www-player.css

31 ms

www-embed-player.js

www-embed-player.js

30 ms

base.js

base.js

31 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff

84 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf

93 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff

99 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf

107 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff

112 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf

112 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aXw.woff

108 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf

112 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff

107 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf

111 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff

111 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

125 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff

126 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf

127 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aXw.woff

126 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf

125 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aXw.woff

124 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf

127 ms

S6u9w4BMUTPHh6UVSwaPHw.woff

S6u9w4BMUTPHh6UVSwaPHw.woff

127 ms

S6u9w4BMUTPHh6UVSwaPHA.ttf

S6u9w4BMUTPHh6UVSwaPHA.ttf

128 ms

S6u9w4BMUTPHh50XSwaPHw.woff

S6u9w4BMUTPHh50XSwaPHw.woff

127 ms

S6u9w4BMUTPHh50XSwaPHA.ttf

S6u9w4BMUTPHh50XSwaPHA.ttf

129 ms

S6uyw4BMUTPHjxAwWA.woff

S6uyw4BMUTPHjxAwWA.woff

128 ms

S6uyw4BMUTPHjxAwWw.ttf

S6uyw4BMUTPHjxAwWw.ttf

129 ms

S6u9w4BMUTPHh7USSwaPHw.woff

S6u9w4BMUTPHh7USSwaPHw.woff

129 ms

S6u9w4BMUTPHh7USSwaPHA.ttf

S6u9w4BMUTPHh7USSwaPHA.ttf

130 ms

S6u8w4BMUTPHh30AUi-s.woff

S6u8w4BMUTPHh30AUi-s.woff

130 ms

S6u8w4BMUTPHh30AUi-v.ttf

S6u8w4BMUTPHh30AUi-v.ttf

132 ms

modules.woff

modules.woff

133 ms

hqdefault.jpg

hqdefault.jpg

563 ms

hqdefault.jpg

hqdefault.jpg

556 ms

PG93VCCnmn8

PG93VCCnmn8

139 ms

Y68LanwOjgk

Y68LanwOjgk

133 ms

EYjk1EEXy_o

EYjk1EEXy_o

134 ms

style.min.css

style.min.css

419 ms

www-player.css

www-player.css

7 ms

www-embed-player.js

www-embed-player.js

31 ms

base.js

base.js

66 ms

Accessibility Review

grow.pe accessibility score

64

Accessibility Issues

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.

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

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

High

Links do not have a discernible name

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

grow.pe 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

Missing source maps for large first-party JavaScript

SEO Factors

grow.pe SEO score

100

Search Engine Optimization Advices

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

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grow.pe can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Grow.pe 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

grow.pe

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