Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

neemu.com

Aumente a Performance do seu E-commerce. Linx Impulse.

Page Load Speed

2.9 sec in total

First Response

26 ms

Resources Loaded

1.3 sec

Page Rendered

1.6 sec

About Website

Click here to check amazing Neemu content for Indonesia. Otherwise, check out these important facts you probably never knew about neemu.com

Soluções para atrair, engajar e reengajar clientes de forma personalizada com os objetivos de cada um. Saiba mais sobre essa tecnologia Linx!

Visit neemu.com

Key Findings

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

Performance Metrics

neemu.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

39/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value2,120 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.072

96/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

26 ms

front-flex.min.css

15 ms

main.css

19 ms

app.css

36 ms

tailwind.css

51 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Neemu.com, 3% (3 requests) were made to Cdn.privacytools.com.br and 1% (1 request) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (267 ms) relates to the external source Linx.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 145.0 kB (24%)

Content Size

603.0 kB

After Optimization

458.0 kB

In fact, the total size of Neemu.com main page is 603.0 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. Only a small number of websites need less resources to load. Images take 434.4 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 141.0 kB

  • Original 168.5 kB
  • After minification 168.5 kB
  • After compression 27.6 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 141.0 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 4.0 kB

  • Original 434.4 kB
  • After minification 430.4 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. Neemu images are well optimized though.

Requests Breakdown

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

Requests Now

94

After Optimization

59

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

Accessibility Review

neemu.com accessibility score

95

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

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

neemu.com best practices score

67

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

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

neemu.com SEO score

92

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

High

Tap targets are not sized appropriately

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

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