Tools & Wizards About Us
tallos.com.pe screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 46

    SEO

    Google-friendlier than
    18% of websites

tallos.com.pe

Tallos

Page Load Speed

1.7 sec in total

First Response

87 ms

Resources Loaded

1 sec

Page Rendered

600 ms

tallos.com.pe screenshot

About Website

Visit tallos.com.pe now to see the best up-to-date Tallos content for Peru and also check out these interesting facts you probably never knew about tallos.com.pe

Visit tallos.com.pe

Key Findings

We analyzed Tallos.com.pe page load time and found that the first response time was 87 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

tallos.com.pe performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value550 ms

53/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value10.5 s

23/100

10%

Network Requests Diagram

public

87 ms

138 ms

gtm.js

70 ms

js

133 ms

bootstrap.min.css

54 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 62% of them (42 requests) were addressed to the original Tallos.com.pe, 22% (15 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (373 ms) belongs to the original domain Tallos.com.pe.

Page Optimization Overview & Recommendations

Page size can be reduced by 649.3 kB (17%)

Content Size

3.9 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tallos.com.pe main page is 3.9 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 3.2 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 137.0 kB

  • Original 151.3 kB
  • After minification 128.1 kB
  • After compression 14.3 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 23.1 kB, which is 15% 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 137.0 kB or 91% of the original size.

Image Optimization

-7%

Potential reduce by 233.6 kB

  • Original 3.2 MB
  • After minification 2.9 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. Tallos images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 67.6 kB

  • Original 249.3 kB
  • After minification 243.8 kB
  • After compression 181.7 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 67.6 kB or 27% of the original size.

CSS Optimization

-74%

Potential reduce by 211.1 kB

  • Original 285.0 kB
  • After minification 195.2 kB
  • After compression 73.9 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. Tallos.com.pe needs all CSS files to be minified and compressed as it can save up to 211.1 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (67%)

Requests Now

49

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

public

public

87 ms

138 ms

gtm.js

gtm.js

70 ms

js

js

133 ms

bootstrap.min.css

bootstrap.min.css

54 ms

font.awesome.min.css

font.awesome.min.css

69 ms

linearicons.min.css

linearicons.min.css

66 ms

swiper-bundle.min.css

swiper-bundle.min.css

93 ms

animate.min.css

animate.min.css

95 ms

jquery-ui.min.css

jquery-ui.min.css

93 ms

nice-select.min.css

nice-select.min.css

97 ms

magnific-popup.css

magnific-popup.css

115 ms

datatables.min.css

datatables.min.css

62 ms

summernote-lite.min.css

summernote-lite.min.css

38 ms

style.css

style.css

210 ms

toastr.css

toastr.css

97 ms

custom.css

custom.css

98 ms

logo.png

logo.png

113 ms

1_flores%20para%20amiga%20o%20enamorada.png

1_flores%20para%20amiga%20o%20enamorada.png

114 ms

2_nacimientos.png

2_nacimientos.png

266 ms

3_arreglos%20florales%20para%20velorios.png

3_arreglos%20florales%20para%20velorios.png

261 ms

4_globos-chocolates.jpg

4_globos-chocolates.jpg

205 ms

5_1.png

5_1.png

265 ms

7_Pink%20Confetti%20Champagne%20Bottle%20Picture%20Birthday%20Cocktail%20Invitation%20(1920%20%C3%97%20896%C2%A0px).png

7_Pink%20Confetti%20Champagne%20Bottle%20Picture%20Birthday%20Cocktail%20Invitation%20(1920%20%C3%97%20896%C2%A0px).png

217 ms

1_frutas.jpg

1_frutas.jpg

265 ms

a46.jpg

a46.jpg

259 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

261 ms

jquery-migrate-3.3.2.min.js

jquery-migrate-3.3.2.min.js

294 ms

modernizr-3.7.1.min.js

modernizr-3.7.1.min.js

292 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

298 ms

swiper-bundle.min.js

swiper-bundle.min.js

368 ms

nice-select.min.js

nice-select.min.js

293 ms

jquery.ajaxchimp.min.js

jquery.ajaxchimp.min.js

295 ms

jquery-ui.min.js

jquery-ui.min.js

373 ms

jquery.countdown.min.js

jquery.countdown.min.js

373 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

371 ms

datatables.min.js

datatables.min.js

86 ms

summernote-lite.min.js

summernote-lite.min.js

53 ms

main.js

main.js

370 ms

toastr.js

toastr.js

371 ms

custom.js

custom.js

371 ms

a57.jpg

a57.jpg

372 ms

1.jpg

1.jpg

373 ms

logo-footer.png

logo-footer.png

373 ms

banco1.jpg

banco1.jpg

325 ms

banco2.png

banco2.png

321 ms

6a6c587a-3ec0-4c6b-98c1-987ea2378c17.js

6a6c587a-3ec0-4c6b-98c1-987ea2378c17.js

97 ms

js

js

95 ms

css2

css2

76 ms

css2

css2

95 ms

css2

css2

97 ms

pxiEyp8kv8JHgFVrFJPUdVNF.woff

pxiEyp8kv8JHgFVrFJPUdVNF.woff

34 ms

pxiByp8kv8JHgFVrLGT9V1hvEv-L.woff

pxiByp8kv8JHgFVrLGT9V1hvEv-L.woff

121 ms

pxiByp8kv8JHgFVrLDz8V1hvEv-L.woff

pxiByp8kv8JHgFVrLDz8V1hvEv-L.woff

123 ms

pxiByp8kv8JHgFVrLFj_V1hvEv-L.woff

pxiByp8kv8JHgFVrLFj_V1hvEv-L.woff

124 ms

pxiGyp8kv8JHgFVrLPTedHFHGPc.woff

pxiGyp8kv8JHgFVrLPTedHFHGPc.woff

125 ms

pxiByp8kv8JHgFVrLEj6V1hvEv-L.woff

pxiByp8kv8JHgFVrLEj6V1hvEv-L.woff

185 ms

pxiByp8kv8JHgFVrLCz7V1hvEv-L.woff

pxiByp8kv8JHgFVrLCz7V1hvEv-L.woff

123 ms

pxiByp8kv8JHgFVrLDD4V1hvEv-L.woff

pxiByp8kv8JHgFVrLDD4V1hvEv-L.woff

122 ms

pxiByp8kv8JHgFVrLBT5V1hvEv-L.woff

pxiByp8kv8JHgFVrLBT5V1hvEv-L.woff

124 ms

RWmMoKWR9v4ksMfaWd_JN-XBg6MKDA.woff

RWmMoKWR9v4ksMfaWd_JN-XBg6MKDA.woff

187 ms

lW-swjwOK3Ps5GSJlNNkMalNpiZe_ldbOR4W776rd3o3K6CdKyE.woff

lW-swjwOK3Ps5GSJlNNkMalNpiZe_ldbOR4W776rd3o3K6CdKyE.woff

317 ms

lW-swjwOK3Ps5GSJlNNkMalNpiZe_ldbOR4W74erd3o3K6CdKyE.woff

lW-swjwOK3Ps5GSJlNNkMalNpiZe_ldbOR4W74erd3o3K6CdKyE.woff

185 ms

lW-swjwOK3Ps5GSJlNNkMalNpiZe_ldbOR4W71msd3o3K6CdKyE.woff

lW-swjwOK3Ps5GSJlNNkMalNpiZe_ldbOR4W71msd3o3K6CdKyE.woff

186 ms

lW-swjwOK3Ps5GSJlNNkMalNpiZe_ldbOR4W7wesd3o3K6CdKyE.woff

lW-swjwOK3Ps5GSJlNNkMalNpiZe_ldbOR4W7wesd3o3K6CdKyE.woff

185 ms

lW-swjwOK3Ps5GSJlNNkMalNpiZe_ldbOR4W71mtd3o3K6CdKyE.woff

lW-swjwOK3Ps5GSJlNNkMalNpiZe_ldbOR4W71mtd3o3K6CdKyE.woff

187 ms

Linearicons-Free.ttf

Linearicons-Free.ttf

120 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

119 ms

Accessibility Review

tallos.com.pe accessibility score

87

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

tallos.com.pe best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

tallos.com.pe SEO score

46

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

tallos.com.pe

Open Graph description is not detected on the main page of Tallos. 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: