Access thunderworx.com. PrimeTel for Home: Internet, Telephony, Mobile, Television

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value20.4 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value560 ms

53/100

30%

CLS (Cumulative Layout Shift)

Value0.344

32/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

thunderworx.com

401 ms

primetel.com.cy

309 ms

primetel.com.cy

840 ms

bzh3pgx.css

97 ms

style.css

277 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Thunderworx.com, 71% (45 requests) were made to Primetel.com.cy and 13% (8 requests) were made to App.blinger.io. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Primetel.com.cy.

Content Size

5.1 MB

After Optimization

4.5 MB

In fact, the total size of Thunderworx.com main page is 5.1 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. 45% of websites need less resources to load. Images take 4.7 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 49.6 kB

Original 61.0 kB
After minification 48.7 kB
After compression 11.5 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 12.4 kB, which is 20% 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 49.6 kB or 81% of the original size.

Image Optimization

-12%

Potential reduce by 561.3 kB

Original 4.7 MB
After minification 4.1 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. Obviously, Thunderworx needs image optimization as it can save up to 561.3 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-23%

Potential reduce by 65.5 kB

Original 284.8 kB
After minification 284.8 kB
After compression 219.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 65.5 kB or 23% of the original size.

CSS Optimization

-0%

Potential reduce by 5 B

Original 75.8 kB
After minification 75.8 kB
After compression 75.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. Thunderworx.com has all CSS files already compressed.

Requests Now

After Optimization

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