Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

bettaterritory.nl

www.bettaterritory.nl

Page Load Speed

2.8 sec in total

First Response

380 ms

Resources Loaded

1.8 sec

Page Rendered

673 ms

bettaterritory.nl screenshot

About Website

Click here to check amazing Bettaterritory content for United States. Otherwise, check out these important facts you probably never knew about bettaterritory.nl

Bettaterritory.nl was created in 2003 to provide information about Betta splendens in a simple and easily accessible manner for both the novice as experienced hobbyist.

Visit bettaterritory.nl

Key Findings

We analyzed Bettaterritory.nl page load time and found that the first response time was 380 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

bettaterritory.nl performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

87/100

10%

LCP (Largest Contentful Paint)

Value12.7 s

0/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value1,230 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

bettaterritory.nl

380 ms

LogoTOP.jpg

335 ms

Button-Home.jpg

276 ms

Button-About%20me.jpg

275 ms

Button-AAB.jpg

349 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 179.5 kB (22%)

Content Size

802.3 kB

After Optimization

622.8 kB

In fact, the total size of Bettaterritory.nl main page is 802.3 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. 15% of websites need less resources to load. Images take 726.3 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 68.5 kB

  • Original 76.0 kB
  • After minification 71.3 kB
  • After compression 7.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. 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 68.5 kB or 90% of the original size.

Image Optimization

-15%

Potential reduce by 111.0 kB

  • Original 726.3 kB
  • After minification 615.3 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. Obviously, Bettaterritory needs image optimization as it can save up to 111.0 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

We found no issues to fix!

Requests Now

14

After Optimization

14

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

Accessibility Review

bettaterritory.nl accessibility score

64

Accessibility Issues

Internationalization and localization

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

Impact

Issue

High

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

Names and labels

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.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

bettaterritory.nl best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

bettaterritory.nl SEO score

67

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bettaterritory.nl 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 Bettaterritory.nl main page’s claimed encoding is windows-1252. 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 Bettaterritory. 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: