Access platypusplatypus.com. Platypus Platypus

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

36/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value1,310 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value7.3 s

49/100

10%

platypusplatypus.com

58 ms

platypusplatypus.com

99 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that all of those requests were addressed to Platypusplatypus.com and no external sources were called. The less responsive or slowest element that took the longest time to load (99 ms) belongs to the original domain Platypusplatypus.com.

Content Size

395.5 kB

After Optimization

241.6 kB

In fact, the total size of Platypusplatypus.com main page is 395.5 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. CSS take 161.5 kB which makes up the majority of the site volume.

HTML Optimization

-56%

Potential reduce by 14.4 kB

Original 25.7 kB
After minification 25.6 kB
After compression 11.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. 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 14.4 kB or 56% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

Original 160.2 kB
After minification 160.2 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. Platypus images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 9.2 kB

Original 48.2 kB
After minification 46.9 kB
After compression 38.9 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 9.2 kB or 19% of the original size.

CSS Optimization

-81%

Potential reduce by 130.3 kB

Original 161.5 kB
After minification 161.1 kB
After compression 31.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. Platypusplatypus.com needs all CSS files to be minified and compressed as it can save up to 130.3 kB or 81% of the original size.

Requests Now

After Optimization

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Platypusplatypus.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Platypusplatypus.com main page’s claimed encoding is . 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

platypusplatypus.com

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