Access gotnextsite.wordpress.com. Got Next | A blog about anything BASKETBALL by Rafa Squillantini and Carlos Syquia

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

48/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value540 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.1 s

3/100

10%

gotnextsite.wordpress.com

8 ms

gotnextsite.wordpress.com

154 ms

101 ms

style.css

98 ms

110 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 10% of them (4 requests) were addressed to the original Gotnextsite.wordpress.com, 20% (8 requests) were made to S2.wp.com and 18% (7 requests) were made to S0.wp.com. The less responsive or slowest element that took the longest time to load (201 ms) belongs to the original domain Gotnextsite.wordpress.com.

Content Size

164.1 kB

After Optimization

163.4 kB

In fact, the total size of Gotnextsite.wordpress.com main page is 164.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Javascripts take 131.0 kB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

Original 0 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. This web page is already compressed.

Image Optimization

-0%

Potential reduce by 0 B

Original 8.2 kB
After minification 8.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. Got Next Site Wordpress images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 629 B

Original 131.0 kB
After minification 131.0 kB
After compression 130.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 162 B

Original 25.0 kB
After minification 25.0 kB
After compression 24.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. Gotnextsite.wordpress.com has all CSS files already compressed.

Requests Now

After Optimization

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

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 keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

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

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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 Gotnextsite.wordpress.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 Gotnextsite.wordpress.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

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