Tools & Wizards About Us
semparar.com.br screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 0

    Best Practices

  • 75

    SEO

    Google-friendlier than
    32% of websites

semparar.com.br

Sem Parar: Ecossistema de Mobilidade | tag de Pedágio, tag para Estacionamento e mais

Page Load Speed

2.8 sec in total

First Response

332 ms

Resources Loaded

2.4 sec

Page Rendered

61 ms

semparar.com.br screenshot

About Website

Click here to check amazing Sem Parar content for Brazil. Otherwise, check out these important facts you probably never knew about semparar.com.br

Aproveite a praticidade da tag Sem Parar para otimizar suas viagens, sem se preocupar com pedágios e estacionamentos, pagando no automático. Com acesso a uma variedade de serviços adicionais através d...

Visit semparar.com.br

Key Findings

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

Performance Metrics

semparar.com.br performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.5 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value2,300 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.061

97/100

15%

TTI (Time to Interactive)

Value22.9 s

1/100

10%

Network Requests Diagram

www.semparar.com.br

332 ms

jquery-1.8.3.min.js

30 ms

swfobject.js

29 ms

vtex.ajax.wait.js

40 ms

vtex.common.js

45 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 12% of them (6 requests) were addressed to the original Semparar.com.br, 20% (10 requests) were made to Semparar.vteximg.com.br and 16% (8 requests) were made to Io.vtex.com.br. The less responsive or slowest element that took the longest time to load (888 ms) relates to the external source Campaigns.grow.up.st.

Page Optimization Overview & Recommendations

Page size can be reduced by 31.3 kB (15%)

Content Size

212.3 kB

After Optimization

181.0 kB

  • HTML
  • JavaScript

In fact, the total size of Semparar.com.br main page is 212.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Javascripts take 196.1 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 11.2 kB

  • Original 16.2 kB
  • After minification 16.0 kB
  • After compression 5.1 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 11.2 kB or 69% of the original size.

JavaScript Optimization

-10%

Potential reduce by 20.1 kB

  • Original 196.1 kB
  • After minification 193.1 kB
  • After compression 175.9 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 41 (87%)

Requests Now

47

After Optimization

6

  • AJAX
  • JavaScript

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

Network Requests Diagram

www.semparar.com.br

www.semparar.com.br

332 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

30 ms

swfobject.js

swfobject.js

29 ms

vtex.ajax.wait.js

vtex.ajax.wait.js

40 ms

vtex.common.js

vtex.common.js

45 ms

render-extension-loader.js

render-extension-loader.js

26 ms

rc.js

rc.js

43 ms

af.js

af.js

44 ms

vtex.tagmanager.helper.js

vtex.tagmanager.helper.js

44 ms

vtex-events-all.min.js

vtex-events-all.min.js

48 ms

vtex-analytics.js

vtex-analytics.js

52 ms

vtex-i18n.min.js

vtex-i18n.min.js

49 ms

underscore-extensions.js

underscore-extensions.js

49 ms

currency-format.min.js

currency-format.min.js

51 ms

dust-core-2.3.5.min.js

dust-core-2.3.5.min.js

47 ms

vtex.min.js

vtex.min.js

49 ms

track.js

track.js

58 ms

thickbox.js

thickbox.js

58 ms

json2.js

json2.js

57 ms

vtex.viewpart.callcenterdisclaimer.js

vtex.viewpart.callcenterdisclaimer.js

59 ms

vtex.viewpart.ajaxloader_v2.js

vtex.viewpart.ajaxloader_v2.js

50 ms

analytics.js

analytics.js

24 ms

gtm.js

gtm.js

87 ms

getProfile

getProfile

116 ms

Track.aspx

Track.aspx

166 ms

client.js

client.js

161 ms

disclaimer

disclaimer

244 ms

destination

destination

46 ms

ld.js

ld.js

89 ms

semparar.js

semparar.js

278 ms

pa_rtg_sempararimm.js

pa_rtg_sempararimm.js

306 ms

fbevents.js

fbevents.js

101 ms

btp.js

btp.js

285 ms

ins.js

ins.js

246 ms

k_semparar.js

k_semparar.js

246 ms

h83gd7h3ed

h83gd7h3ed

133 ms

socital.js

socital.js

888 ms

86194454.js

86194454.js

489 ms

10041574-10041797.js

10041574-10041797.js

368 ms

kameleoon.js

kameleoon.js

244 ms

amzn.js

amzn.js

131 ms

lib.js

lib.js

325 ms

js

js

130 ms

js

js

158 ms

376 ms

syncframe

syncframe

159 ms

clarity.js

clarity.js

91 ms

event

event

31 ms

snippet.js

snippet.js

27 ms

socital-3.11.0.js

socital-3.11.0.js

544 ms

Accessibility Review

semparar.com.br accessibility score

72

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

ARIA IDs are not unique

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

SEO Factors

semparar.com.br SEO score

75

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

High

Image elements do not have [alt] attributes

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Semparar.com.br can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Semparar.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

semparar.com.br

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