Tools & Wizards About Us
my-wight.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

my-wight.com

Page Load Speed

11.6 sec in total

First Response

1.3 sec

Resources Loaded

8.8 sec

Page Rendered

1.6 sec

my-wight.com screenshot

About Website

Welcome to my-wight.com homepage info - get ready to check My Wight best content right away, or after learning these important things about my-wight.com

WIGHT: la lampada che reinventa la luce

Visit my-wight.com

Key Findings

We analyzed My-wight.com page load time and found that the first response time was 1.3 sec and then it took 10.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

my-wight.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value1,200 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.768

5/100

15%

TTI (Time to Interactive)

Value21.1 s

1/100

10%

Network Requests Diagram

my-wight.com

1278 ms

reset.min.css

261 ms

css

24 ms

jquery.min.js

31 ms

jquery-migrate-1.1.0.js

4 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 72% of them (58 requests) were addressed to the original My-wight.com, 7% (6 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain My-wight.com.

Page Optimization Overview & Recommendations

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

Content Size

2.4 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of My-wight.com main page is 2.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 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 26.8 kB

  • Original 34.7 kB
  • After minification 27.5 kB
  • After compression 7.8 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 7.2 kB, which is 21% 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 26.8 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 63.0 kB

  • Original 1.9 MB
  • After minification 1.8 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. My Wight images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 136.5 kB

  • Original 232.1 kB
  • After minification 228.6 kB
  • After compression 95.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 136.5 kB or 59% of the original size.

CSS Optimization

-83%

Potential reduce by 217.9 kB

  • Original 263.2 kB
  • After minification 257.1 kB
  • After compression 45.2 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. My-wight.com needs all CSS files to be minified and compressed as it can save up to 217.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (20%)

Requests Now

74

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

my-wight.com

my-wight.com

1278 ms

reset.min.css

reset.min.css

261 ms

css

css

24 ms

jquery.min.js

jquery.min.js

31 ms

jquery-migrate-1.1.0.js

jquery-migrate-1.1.0.js

4 ms

jquery.fittext.js

jquery.fittext.js

277 ms

jqModal.js

jqModal.js

280 ms

facebook_feed.js

facebook_feed.js

283 ms

wight-style.css

wight-style.css

1380 ms

wight.js

wight.js

1242 ms

ga.js

ga.js

80 ms

minilogo.png

minilogo.png

174 ms

14_169.jpg

14_169.jpg

600 ms

transp_1280x720.png

transp_1280x720.png

261 ms

scroll.png

scroll.png

281 ms

sfondo1.jpg

sfondo1.jpg

631 ms

devices2.png

devices2.png

1266 ms

presto.png

presto.png

1247 ms

sfondo_blu.jpg

sfondo_blu.jpg

1582 ms

sfondo2.jpg

sfondo2.jpg

1504 ms

wight_web_app.png

wight_web_app.png

1487 ms

lamp_color.png

lamp_color.png

2096 ms

polaroid.jpg

polaroid.jpg

2008 ms

potenza_lampadine.png

potenza_lampadine.png

1872 ms

uguale.png

uguale.png

1779 ms

cubo_84.png

cubo_84.png

2168 ms

figure_sx1.png

figure_sx1.png

1994 ms

figure_dx_1.png

figure_dx_1.png

2041 ms

figure_sx2.png

figure_sx2.png

2235 ms

figure_dx_2.png

figure_dx_2.png

2252 ms

cube_open.png

cube_open.png

2291 ms

cubo_no_84.png

cubo_no_84.png

2798 ms

phone_hand.png

phone_hand.png

2774 ms

11B_169.jpg

11B_169.jpg

2732 ms

1_169.jpg

1_169.jpg

3318 ms

15_169.jpg

15_169.jpg

3495 ms

1.png

1.png

3458 ms

2.png

2.png

3694 ms

6.png

6.png

3673 ms

3.png

3.png

3853 ms

9.jpg

9.jpg

3731 ms

8.png

8.png

4061 ms

veratti.jpg

veratti.jpg

4061 ms

7.png

7.png

4089 ms

nss.jpg

nss.jpg

4052 ms

10.jpg

10.jpg

4218 ms

11.jpg

11.jpg

4246 ms

toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf

toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf

28 ms

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

29 ms

toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf

toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf

29 ms

toadOcfmlt9b38dHJxOBGEMbjGELOEJD5J8DUmxkO-A.ttf

toadOcfmlt9b38dHJxOBGEMbjGELOEJD5J8DUmxkO-A.ttf

29 ms

__utm.gif

__utm.gif

23 ms

all.js

all.js

6 ms

118 ms

12.jpg

12.jpg

4135 ms

xd_arbiter.php

xd_arbiter.php

30 ms

xd_arbiter.php

xd_arbiter.php

44 ms

8m_tf2o0vws

8m_tf2o0vws

89 ms

7_169.jpg

7_169.jpg

4342 ms

facebook_miniball.png

facebook_miniball.png

4060 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

21 ms

www-embed-player.js

www-embed-player.js

45 ms

base.js

base.js

66 ms

Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js

Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js

29 ms

ad_status.js

ad_status.js

28 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

24 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

27 ms

img_works.png

img_works.png

4530 ms

preordine_chiuso.png

preordine_chiuso.png

3981 ms

newmodal_bg.png

newmodal_bg.png

3603 ms

close_small.png

close_small.png

3596 ms

modal_priceball.png

modal_priceball.png

3618 ms

paypal.png

paypal.png

3901 ms

credit.png

credit.png

3968 ms

facebook_ball.png

facebook_ball.png

3784 ms

facebook_condividi.png

facebook_condividi.png

3950 ms

mail.png

mail.png

4067 ms

close.png

close.png

4087 ms

newmodal_bg_small.png

newmodal_bg_small.png

4064 ms

iubenda.js

iubenda.js

15 ms

ping

ping

70 ms

Accessibility Review

my-wight.com accessibility score

51

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

my-wight.com best practices score

75

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

my-wight.com SEO score

67

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    IT

  • Language Claimed

    IT

  • Encoding

    UTF-8

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

my-wight.com

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