Tools & Wizards About Us
nayan.be screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

nayan.be

naYan - Ecommerce Agency | Scaling Your Ecommerce

Page Load Speed

4 sec in total

First Response

286 ms

Resources Loaded

2.7 sec

Page Rendered

1.1 sec

nayan.be screenshot

About Website

Welcome to nayan.be homepage info - get ready to check NaYan best content right away, or after learning these important things about nayan.be

naYan is an ecommerce agency highly skilled in ecommerce, digital marketing, customer experience & marketplace services for international brands

Visit nayan.be

Key Findings

We analyzed Nayan.be page load time and found that the first response time was 286 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

nayan.be performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value2,110 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

Network Requests Diagram

nayan.be

286 ms

nayan.be

488 ms

uc.js

27 ms

style.min.css

94 ms

theme.min.css

186 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 84% of them (76 requests) were addressed to the original Nayan.be, 10% (9 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (859 ms) belongs to the original domain Nayan.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 539.8 kB (16%)

Content Size

3.4 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Nayan.be main page is 3.4 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. 70% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 152.5 kB

  • Original 177.8 kB
  • After minification 171.9 kB
  • After compression 25.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. 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 152.5 kB or 86% of the original size.

Image Optimization

-10%

Potential reduce by 298.1 kB

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

JavaScript Optimization

-29%

Potential reduce by 89.3 kB

  • Original 313.0 kB
  • After minification 313.0 kB
  • After compression 223.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 89.3 kB or 29% of the original size.

Requests Breakdown

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

Requests Now

77

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nayan.be

nayan.be

286 ms

nayan.be

nayan.be

488 ms

uc.js

uc.js

27 ms

style.min.css

style.min.css

94 ms

theme.min.css

theme.min.css

186 ms

header-footer.min.css

header-footer.min.css

274 ms

frontend-lite.min.css

frontend-lite.min.css

278 ms

post-16.css

post-16.css

275 ms

elementor-icons.min.css

elementor-icons.min.css

292 ms

swiper.min.css

swiper.min.css

285 ms

frontend-lite.min.css

frontend-lite.min.css

293 ms

all.min.css

all.min.css

378 ms

v4-shims.min.css

v4-shims.min.css

375 ms

global.css

global.css

371 ms

post-11.css

post-11.css

381 ms

post-208.css

post-208.css

384 ms

post-222.css

post-222.css

385 ms

post-7573.css

post-7573.css

464 ms

style.css

style.css

468 ms

fontawesome.min.css

fontawesome.min.css

469 ms

solid.min.css

solid.min.css

473 ms

brands.min.css

brands.min.css

473 ms

v4-shims.min.js

v4-shims.min.js

478 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

560 ms

widget-call-to-action.min.css

widget-call-to-action.min.css

559 ms

widget-posts.min.css

widget-posts.min.css

561 ms

widget-icon-list.min.css

widget-icon-list.min.css

562 ms

language-switcher.min.css

language-switcher.min.css

565 ms

post-784.css

post-784.css

566 ms

animations.min.css

animations.min.css

651 ms

hello-frontend.min.js

hello-frontend.min.js

742 ms

jquery.min.js

jquery.min.js

802 ms

jquery-migrate.min.js

jquery-migrate.min.js

741 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

743 ms

imagesloaded.min.js

imagesloaded.min.js

743 ms

api.js

api.js

37 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

801 ms

webpack.runtime.min.js

webpack.runtime.min.js

819 ms

frontend-modules.min.js

frontend-modules.min.js

840 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

819 ms

css

css

86 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

734 ms

wp-polyfill.min.js

wp-polyfill.min.js

756 ms

hooks.min.js

hooks.min.js

579 ms

i18n.min.js

i18n.min.js

575 ms

frontend.min.js

frontend.min.js

614 ms

waypoints.min.js

waypoints.min.js

612 ms

core.min.js

core.min.js

648 ms

frontend.min.js

frontend.min.js

684 ms

elements-handlers.min.js

elements-handlers.min.js

605 ms

jquery.sticky.min.js

jquery.sticky.min.js

603 ms

lazyload.min.js

lazyload.min.js

612 ms

gtm.js

gtm.js

95 ms

js

js

143 ms

samson-ZGjbiukp_-A-unsplash-1.webp

samson-ZGjbiukp_-A-unsplash-1.webp

457 ms

Nayan-Favicon-icon.png

Nayan-Favicon-icon.png

368 ms

nayan.be

nayan.be

370 ms

nasa-Q1p7bh3SHj8-unsplash.webp

nasa-Q1p7bh3SHj8-unsplash.webp

458 ms

Nayan-Favicon-icon-white.png

Nayan-Favicon-icon-white.png

460 ms

qFda35WCmI96Ajtm83upeyoaX6QPnlo6zvPbPpqP.ttf

qFda35WCmI96Ajtm83upeyoaX6QPnlo6zvPbPpqP.ttf

142 ms

qFda35WCmI96Ajtm83upeyoaX6QPnlo6_PPbPpqP.ttf

qFda35WCmI96Ajtm83upeyoaX6QPnlo6_PPbPpqP.ttf

142 ms

qFda35WCmI96Ajtm83upeyoaX6QPnlo6ovPbPpqP.ttf

qFda35WCmI96Ajtm83upeyoaX6QPnlo6ovPbPpqP.ttf

161 ms

qFda35WCmI96Ajtm83upeyoaX6QPnlo6fPPbPpqP.ttf

qFda35WCmI96Ajtm83upeyoaX6QPnlo6fPPbPpqP.ttf

222 ms

qFda35WCmI96Ajtm83upeyoaX6QPnlo6_PLbPpqP.ttf

qFda35WCmI96Ajtm83upeyoaX6QPnlo6_PLbPpqP.ttf

236 ms

qFda35WCmI96Ajtm83upeyoaX6QPnlo6IvTbPpqP.ttf

qFda35WCmI96Ajtm83upeyoaX6QPnlo6IvTbPpqP.ttf

236 ms

qFda35WCmI96Ajtm83upeyoaX6QPnlo6G_TbPpqP.ttf

qFda35WCmI96Ajtm83upeyoaX6QPnlo6G_TbPpqP.ttf

235 ms

qFda35WCmI96Ajtm83upeyoaX6QPnlo6fPTbPpqP.ttf

qFda35WCmI96Ajtm83upeyoaX6QPnlo6fPTbPpqP.ttf

271 ms

qFda35WCmI96Ajtm83upeyoaX6QPnlo6VfTbPpqP.ttf

qFda35WCmI96Ajtm83upeyoaX6QPnlo6VfTbPpqP.ttf

218 ms

fa-solid-900.woff

fa-solid-900.woff

387 ms

fa-regular-400.woff

fa-regular-400.woff

376 ms

fa-brands-400.woff

fa-brands-400.woff

466 ms

recaptcha__en.js

recaptcha__en.js

28 ms

Nayan-Official-Logo-black-1024x208.png

Nayan-Official-Logo-black-1024x208.png

203 ms

Nayan-Favicon-icon-1024x972.png

Nayan-Favicon-icon-1024x972.png

217 ms

DSC_8401.jpg

DSC_8401.jpg

389 ms

230622_SAMSONITE_EXTENSION_CAMPAIGN_01_0065-ORIGINAL-1.webp

230622_SAMSONITE_EXTENSION_CAMPAIGN_01_0065-ORIGINAL-1.webp

218 ms

kitchenaid-mp-min-1024x576.jpg

kitchenaid-mp-min-1024x576.jpg

219 ms

lp_renee-piano-1-1-1024x768.webp

lp_renee-piano-1-1-1024x768.webp

304 ms

Salesforce-logo.png

Salesforce-logo.png

301 ms

google-logo-1024x536.jpg

google-logo-1024x536.jpg

308 ms

Proximity-insight-logo-1024x205.png

Proximity-insight-logo-1024x205.png

315 ms

Adyen-logo-1024x331.png

Adyen-logo-1024x331.png

308 ms

mp-amazon.jpg

mp-amazon.jpg

392 ms

Shopware-logo.webp

Shopware-logo.webp

401 ms

iStock-1322865839-min-1024x683.jpg

iStock-1322865839-min-1024x683.jpg

403 ms

IMG_9315-1-1024x510.jpg

IMG_9315-1-1024x510.jpg

400 ms

iStock-1146839170-min-1024x768.jpg

iStock-1146839170-min-1024x768.jpg

498 ms

nayan-logo-slogan-wit.png

nayan-logo-slogan-wit.png

484 ms

Google-Partner-Nayan.png

Google-Partner-Nayan.png

485 ms

amazon_ads_verified_partner.png

amazon_ads_verified_partner.png

492 ms

nayan-.png

nayan-.png

859 ms

Accessibility Review

nayan.be accessibility score

89

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

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

Links do not have a discernible name

Best Practices

nayan.be 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

SEO Factors

nayan.be SEO score

92

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

nayan.be

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