Access pigwa.net. pigwa.net

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.8 s

100/100

25%

SI (Speed Index)

Value0.9 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.8 s

100/100

10%

pigwa.net

275 ms

style.css

145 ms

atari.gif

245 ms

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

Content Size

1.5 kB

After Optimization

760 B

In fact, the total size of Pigwa.net main page is 1.5 kB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. CSS take 914 B which makes up the majority of the site volume.

HTML Optimization

-34%

Potential reduce by 193 B

Original 567 B
After minification 563 B
After compression 374 B

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 193 B or 34% of the original size.

CSS Optimization

-58%

Potential reduce by 528 B

Original 914 B
After minification 772 B
After compression 386 B

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. Pigwa.net needs all CSS files to be minified and compressed as it can save up to 528 B or 58% of the original size.

Requests Now

After Optimization

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pigwa. According to our analytics all requests are already optimized.

Accessibility Issues

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Search Engine Optimization Advices

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

High

Image elements do not have [alt] attributes

Language and Encoding

Language Detected

N/A
Language Claimed

N/A
Encoding

ISO-8859-2

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pigwa.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 Pigwa.net 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

pigwa.net

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