Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

neosens.com

Neosens| New Collection | Calzado Premium de Diseño y Calidad Calzado online para hombre y mujer - Calzado de Diseño y Calidad - Neosens

Page Load Speed

21.5 sec in total

First Response

130 ms

Resources Loaded

20.4 sec

Page Rendered

989 ms

neosens.com screenshot

About Website

Visit neosens.com now to see the best up-to-date Neosens content for Spain and also check out these interesting facts you probably never knew about neosens.com

Calzado online para hombre y mujer. Zapatos cómodos, frescos, flexibles e innovadores inspirados en la naturaleza para personas ocupadas

Visit neosens.com

Key Findings

We analyzed Neosens.com page load time and found that the first response time was 130 ms and then it took 21.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

neosens.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value26.4 s

0/100

25%

SI (Speed Index)

Value16.1 s

0/100

10%

TBT (Total Blocking Time)

Value8,180 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value36.0 s

0/100

10%

Network Requests Diagram

130 ms

b0e2150da26b2ac00154d164c575abe1.min.css

17 ms

require.min.js

16 ms

requirejs-min-resolver.min.js

14 ms

mixins.min.js

14 ms

Our browser made a total of 330 requests to load all elements on the main page. We found that 86% of them (285 requests) were addressed to the original Neosens.com, 4% (12 requests) were made to Polyfill.io and 2% (6 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Wisepops.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 419.1 kB (18%)

Content Size

2.3 MB

After Optimization

1.8 MB

In fact, the total size of Neosens.com main page is 2.3 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 187.1 kB

  • Original 219.5 kB
  • After minification 195.6 kB
  • After compression 32.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.8 kB, which is 11% 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 187.1 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 1.2 kB

  • Original 735.6 kB
  • After minification 734.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. Neosens images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 211.4 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 892.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 211.4 kB or 19% of the original size.

CSS Optimization

-9%

Potential reduce by 19.4 kB

  • Original 207.9 kB
  • After minification 207.9 kB
  • After compression 188.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. Neosens.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 264 (83%)

Requests Now

320

After Optimization

56

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

Accessibility Review

neosens.com accessibility score

93

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

button, link, and menuitem elements do not have accessible names.

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

neosens.com best practices score

92

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

Page has valid source maps

SEO Factors

neosens.com SEO score

89

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

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Neosens.com 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 Neosens.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 description is not detected on the main page of Neosens. 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: