Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

planex.net

PLANEX COMMUNICATIONS

Page Load Speed

6.3 sec in total

First Response

557 ms

Resources Loaded

5.5 sec

Page Rendered

292 ms

planex.net screenshot

About Website

Click here to check amazing PLANEX content for United States. Otherwise, check out these important facts you probably never knew about planex.net

Visit planex.net

Key Findings

We analyzed Planex.net page load time and found that the first response time was 557 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

planex.net performance score

0

Network Requests Diagram

planex.net

557 ms

www.planex.net

983 ms

main.css

937 ms

grid.css

911 ms

logo.png

547 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 95% of them (19 requests) were addressed to the original Planex.net, 5% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Planex.net.

Page Optimization Overview & Recommendations

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

Content Size

1.6 MB

After Optimization

1.4 MB

In fact, the total size of Planex.net main page is 1.6 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. Only 10% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 6.6 kB

  • Original 8.0 kB
  • After minification 5.5 kB
  • After compression 1.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. This page needs HTML code to be minified as it can gain 2.5 kB, which is 31% 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 6.6 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 81.0 kB

  • Original 1.4 MB
  • After minification 1.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. PLANEX images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 84.8 kB

  • Original 127.0 kB
  • After minification 120.0 kB
  • After compression 42.2 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 84.8 kB or 67% of the original size.

CSS Optimization

-86%

Potential reduce by 84.1 kB

  • Original 97.5 kB
  • After minification 72.6 kB
  • After compression 13.4 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. Planex.net needs all CSS files to be minified and compressed as it can save up to 84.1 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (44%)

Requests Now

18

After Optimization

10

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

SEO Factors

planex.net SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Planex.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Planex.net 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

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