Tools & Wizards About Us
u3d.pl screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

u3d.pl

U3D.net - Dostarczamy Internet... Każdego dnia bez przerwy!

Page Load Speed

4.1 sec in total

First Response

286 ms

Resources Loaded

3.7 sec

Page Rendered

120 ms

u3d.pl screenshot

About Website

Welcome to u3d.pl homepage info - get ready to check U3D best content right away, or after learning these important things about u3d.pl

Dostarczamy Internet... Pewnie! Każdego dnia, bez przerwy. Szybki i niezawodny Internet bezprzewodowy Gorzów Wielkopolski i okolice.

Visit u3d.pl

Key Findings

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

Performance Metrics

u3d.pl performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value16.6 s

0/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value1,100 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value1.063

2/100

15%

TTI (Time to Interactive)

Value17.1 s

4/100

10%

Network Requests Diagram

u3d.pl

286 ms

u3d.net

457 ms

screen.css

358 ms

cookies.js

360 ms

analytics.js

18 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original U3d.pl, 42% (20 requests) were made to Static.xx.fbcdn.net and 19% (9 requests) were made to U3d.net. The less responsive or slowest element that took the longest time to load (918 ms) relates to the external source Scontent.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 52.7 kB (21%)

Content Size

252.3 kB

After Optimization

199.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-69%

Potential reduce by 11.1 kB

  • Original 16.0 kB
  • After minification 15.9 kB
  • After compression 4.9 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 11.1 kB or 69% of the original size.

Image Optimization

-2%

Potential reduce by 3.5 kB

  • Original 157.8 kB
  • After minification 154.3 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. U3D images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 32.8 kB

  • Original 71.5 kB
  • After minification 71.3 kB
  • After compression 38.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 32.8 kB or 46% of the original size.

CSS Optimization

-75%

Potential reduce by 5.2 kB

  • Original 7.0 kB
  • After minification 5.5 kB
  • After compression 1.8 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. U3d.pl needs all CSS files to be minified and compressed as it can save up to 5.2 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (59%)

Requests Now

46

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

u3d.pl

u3d.pl

286 ms

u3d.net

u3d.net

457 ms

screen.css

screen.css

358 ms

cookies.js

cookies.js

360 ms

analytics.js

analytics.js

18 ms

technologie.png

technologie.png

178 ms

header2.jpg

header2.jpg

353 ms

bg_menu1.gif

bg_menu1.gif

179 ms

pierwsza.jpg

pierwsza.jpg

358 ms

stopka.png

stopka.png

181 ms

all.js

all.js

269 ms

dc.js

dc.js

34 ms

collect

collect

10 ms

__utm.gif

__utm.gif

12 ms

64 ms

xd_arbiter.php

xd_arbiter.php

235 ms

xd_arbiter.php

xd_arbiter.php

451 ms

print.css

print.css

187 ms

like_box.php

like_box.php

156 ms

ebiMDO3r-8l.css

ebiMDO3r-8l.css

284 ms

jGc-59L_9lo.css

jGc-59L_9lo.css

354 ms

k5BhlqovqZn.css

k5BhlqovqZn.css

421 ms

TKuNj0xVh4A.js

TKuNj0xVh4A.js

555 ms

GIPX3YHTHu1.js

GIPX3YHTHu1.js

624 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

488 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

491 ms

OloiM1PZafe.js

OloiM1PZafe.js

488 ms

LTv6ZK-5zxz.js

LTv6ZK-5zxz.js

689 ms

1FCa-btixu2.js

1FCa-btixu2.js

620 ms

Oagsvfb4VWi.js

Oagsvfb4VWi.js

636 ms

pObvZSrFc_4.js

pObvZSrFc_4.js

637 ms

HgJbVwzBr8E.js

HgJbVwzBr8E.js

635 ms

H3EKDTObx05.js

H3EKDTObx05.js

720 ms

OZFAYTv-ZUg.js

OZFAYTv-ZUg.js

723 ms

11021080_1051005974913262_5285825576558800708_n.jpg

11021080_1051005974913262_5285825576558800708_n.jpg

535 ms

764_582647068415824_1952817326_n.jpg

764_582647068415824_1952817326_n.jpg

662 ms

12647000_966973206724967_7888108804980954522_n.jpg

12647000_966973206724967_7888108804980954522_n.jpg

730 ms

10407115_859837527369629_331394157911635710_n.jpg

10407115_859837527369629_331394157911635710_n.jpg

918 ms

12678_566747663385965_252306596_n.jpg

12678_566747663385965_252306596_n.jpg

737 ms

10401990_1073308479417217_1241110174959041245_n.jpg

10401990_1073308479417217_1241110174959041245_n.jpg

801 ms

12669440_943798375697073_6099909333538896412_n.jpg

12669440_943798375697073_6099909333538896412_n.jpg

800 ms

1379841_10150004552801901_469209496895221757_n.jpg

1379841_10150004552801901_469209496895221757_n.jpg

735 ms

11889548_1007839595934193_4775030395112251448_n.jpg

11889548_1007839595934193_4775030395112251448_n.jpg

800 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

86 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

87 ms

gxbPuQdXIZP.png

gxbPuQdXIZP.png

69 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

69 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

135 ms

Accessibility Review

u3d.pl accessibility score

89

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

Best Practices

u3d.pl best practices score

67

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

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

u3d.pl SEO score

83

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    PL

  • Language Claimed

    EN

  • Encoding

    ISO-8859-2

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise U3d.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it does not match the claimed English language. Our system also found out that U3d.pl main page’s claimed encoding is iso-8859-2. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

u3d.pl

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