Tools & Wizards About Us
nolar.com.br screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

nolar.com.br

NOLAR - Empregada Doméstica - Férias, demissão, recibos e muito mais

Page Load Speed

2 sec in total

First Response

104 ms

Resources Loaded

1.4 sec

Page Rendered

448 ms

nolar.com.br screenshot

About Website

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

Integrado ao eSocial Doméstico para cálculos trabalhistas de empregada doméstica. Recibo de salário, rescisão, férias, 13º salário e mais.

Visit nolar.com.br

Key Findings

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

Performance Metrics

nolar.com.br performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value5,520 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.002

2/100

15%

TTI (Time to Interactive)

Value22.9 s

1/100

10%

Network Requests Diagram

nolar.com.br

104 ms

www.nolar.com.br

31 ms

style-frontend-pro.css

11 ms

stickThis.css

20 ms

style.min.css

19 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 84% of them (36 requests) were addressed to the original Nolar.com.br, 12% (5 requests) were made to Youtube.com and 2% (1 request) were made to Kit.fontawesome.com. The less responsive or slowest element that took the longest time to load (222 ms) relates to the external source Youtube.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 808.2 kB (48%)

Content Size

1.7 MB

After Optimization

861.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nolar.com.br main page is 1.7 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. Javascripts take 728.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 171.4 kB

  • Original 210.6 kB
  • After minification 205.8 kB
  • After compression 39.2 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 171.4 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 20.2 kB

  • Original 481.0 kB
  • After minification 460.8 kB

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. NOLAR images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 448.2 kB

  • Original 728.9 kB
  • After minification 719.0 kB
  • After compression 280.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 448.2 kB or 61% of the original size.

CSS Optimization

-67%

Potential reduce by 168.4 kB

  • Original 249.6 kB
  • After minification 249.6 kB
  • After compression 81.2 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. Nolar.com.br needs all CSS files to be minified and compressed as it can save up to 168.4 kB or 67% of the original size.

Requests Breakdown

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

Requests Now

39

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nolar.com.br

nolar.com.br

104 ms

www.nolar.com.br

www.nolar.com.br

31 ms

style-frontend-pro.css

style-frontend-pro.css

11 ms

stickThis.css

stickThis.css

20 ms

style.min.css

style.min.css

19 ms

jquery.min.js

jquery.min.js

26 ms

jquery-migrate.min.js

jquery-migrate.min.js

25 ms

jq-sticky-anything.js

jq-sticky-anything.js

25 ms

15eb71030d.js

15eb71030d.js

178 ms

js

js

140 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

21 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

22 ms

front-end-free.js

front-end-free.js

67 ms

stickThis.js

stickThis.js

73 ms

scripts.min.js

scripts.min.js

76 ms

jquery.fitvids.js

jquery.fitvids.js

67 ms

frontend-bundle.min.js

frontend-bundle.min.js

69 ms

common.js

common.js

74 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

74 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

72 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

113 ms

kk0cuNLpfrQ

kk0cuNLpfrQ

222 ms

logo_nolar_186x86.png

logo_nolar_186x86.png

66 ms

background_nolar_mobile_done.png

background_nolar_mobile_done.png

74 ms

button_google_large.png

button_google_large.png

70 ms

button_form_large-1.png

button_form_large-1.png

72 ms

google-signup.png

google-signup.png

72 ms

logo_Esocial.png

logo_Esocial.png

72 ms

icon_1.png

icon_1.png

72 ms

icon_4.png

icon_4.png

95 ms

icon_2.png

icon_2.png

94 ms

icon_3.png

icon_3.png

95 ms

google-signup-300x47.png

google-signup-300x47.png

95 ms

ferias-de-empregada-domestica.png

ferias-de-empregada-domestica.png

98 ms

contrato-empregada-domestica-1024x536.png

contrato-empregada-domestica-1024x536.png

98 ms

logo.png

logo.png

97 ms

banner_principal_nolar_novo.jpg

banner_principal_nolar_novo.jpg

39 ms

bg_fotter.png

bg_fotter.png

37 ms

kk0cuNLpfrQ

kk0cuNLpfrQ

91 ms

modules.ttf

modules.ttf

4 ms

www-player.css

www-player.css

7 ms

www-embed-player.js

www-embed-player.js

29 ms

base.js

base.js

61 ms

Accessibility Review

nolar.com.br accessibility score

80

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.

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

nolar.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

nolar.com.br SEO score

93

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

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 Nolar.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 Nolar.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

nolar.com.br

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