Tools & Wizards About Us
nwai.pl screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

nwai.pl

NWAI.pl - Dom maklerski

Page Load Speed

7.4 sec in total

First Response

259 ms

Resources Loaded

6.6 sec

Page Rendered

515 ms

nwai.pl screenshot

About Website

Visit nwai.pl now to see the best up-to-date NWAI content for Poland and also check out these interesting facts you probably never knew about nwai.pl

Działamy od 2007r, w tym czasie współpracując z ponad 100 emitentami zrealizowaliśmy transakcje o wartości ponad 3 mld zł. Zapewniamy kompleksową obsługę

Visit nwai.pl

Key Findings

We analyzed Nwai.pl page load time and found that the first response time was 259 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

nwai.pl performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value6.0 s

65/100

10%

Network Requests Diagram

nwai.pl

259 ms

nwai.pl

1487 ms

js

68 ms

bootstrap.css

230 ms

main.css

463 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 81% of them (34 requests) were addressed to the original Nwai.pl, 12% (5 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Nwai.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 494.3 kB (7%)

Content Size

6.8 MB

After Optimization

6.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nwai.pl main page is 6.8 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. 40% of websites need less resources to load. Images take 6.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 31.7 kB

  • Original 38.2 kB
  • After minification 24.9 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 13.4 kB, which is 35% 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 31.7 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 164.1 kB

  • Original 6.4 MB
  • After minification 6.3 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. NWAI images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 138.3 kB

  • Original 199.8 kB
  • After minification 156.1 kB
  • After compression 61.5 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 138.3 kB or 69% of the original size.

CSS Optimization

-85%

Potential reduce by 160.3 kB

  • Original 188.8 kB
  • After minification 163.1 kB
  • After compression 28.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. Nwai.pl needs all CSS files to be minified and compressed as it can save up to 160.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (40%)

Requests Now

35

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nwai.pl

nwai.pl

259 ms

nwai.pl

nwai.pl

1487 ms

js

js

68 ms

bootstrap.css

bootstrap.css

230 ms

main.css

main.css

463 ms

sol.css

sol.css

376 ms

lightbox.css

lightbox.css

365 ms

cookies.css

cookies.css

342 ms

cookies.js

cookies.js

374 ms

jquery.js

jquery.js

372 ms

script.js

script.js

455 ms

sol.js

sol.js

481 ms

bootstrap.min.js

bootstrap.min.js

489 ms

lightbox.js

lightbox.js

499 ms

slider_dot.js

slider_dot.js

500 ms

d3.min.js

d3.min.js

81 ms

d3pie.js

d3pie.js

684 ms

css

css

40 ms

close.png

close.png

129 ms

loading.gif

loading.gif

137 ms

prev.png

prev.png

145 ms

next.png

next.png

182 ms

main_logo.png

main_logo.png

173 ms

menu_arr_down.png

menu_arr_down.png

264 ms

search_icon.png

search_icon.png

249 ms

15042522941000_socail-icon1.png

15042522941000_socail-icon1.png

253 ms

15081493791000_socail-icon2.png

15081493791000_socail-icon2.png

275 ms

15068754776732_15064309955085-0.jpg

15068754776732_15064309955085-0.jpg

1335 ms

16370672259013_50237851-duzy.jpg

16370672259013_50237851-duzy.jpg

1978 ms

16777518844202_nwai.png

16777518844202_nwai.png

1141 ms

top_cover.png

top_cover.png

705 ms

S6uyw4BMUTPHjxAwWw.ttf

S6uyw4BMUTPHjxAwWw.ttf

46 ms

S6u9w4BMUTPHh7USSwaPHA.ttf

S6u9w4BMUTPHh7USSwaPHA.ttf

55 ms

S6u8w4BMUTPHh30AUi-v.ttf

S6u8w4BMUTPHh30AUi-v.ttf

62 ms

S6u9w4BMUTPHh6UVSwaPHA.ttf

S6u9w4BMUTPHh6UVSwaPHA.ttf

61 ms

S6u9w4BMUTPHh50XSwaPHA.ttf

S6u9w4BMUTPHh50XSwaPHA.ttf

62 ms

16370669351224_50237851-maly.jpg

16370669351224_50237851-maly.jpg

1014 ms

17158440325605_miesiecznik.PNG

17158440325605_miesiecznik.PNG

762 ms

15066123314102_15064367327523-animacja.jpg

15066123314102_15064367327523-animacja.jpg

4154 ms

normal_15059298613111_shutterstock-534098647.jpg

normal_15059298613111_shutterstock-534098647.jpg

1536 ms

normal_15059295175950_b.jpg

normal_15059295175950_b.jpg

2209 ms

normal_15041836166771_home-img3.jpg

normal_15041836166771_home-img3.jpg

1478 ms

Accessibility Review

nwai.pl accessibility score

86

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

nwai.pl best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

nwai.pl 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

Language and Encoding

  • Language Detected

    PL

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nwai.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Nwai.pl 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

nwai.pl

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