Access fiskebat.no. Fiskebåt

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.388

26/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

fiskebat.no

985 ms

ofj4ncw.js

145 ms

StyleSheet.css

309 ms

Custom.css

210 ms

JScript.js

247 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 38% of them (45 requests) were addressed to the original Fiskebat.no, 23% (27 requests) were made to Static.xx.fbcdn.net and 8% (9 requests) were made to Godfisk.no. The less responsive or slowest element that took the longest time to load (985 ms) belongs to the original domain Fiskebat.no.

Content Size

577.5 kB

After Optimization

460.8 kB

In fact, the total size of Fiskebat.no main page is 577.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 461.5 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 43.6 kB

Original 51.9 kB
After minification 51.2 kB
After compression 8.4 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 43.6 kB or 84% of the original size.

Image Optimization

-7%

Potential reduce by 33.2 kB

Original 461.5 kB
After minification 428.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. Fiskebat images are well optimized though.

JavaScript Optimization

-30%

Potential reduce by 8.5 kB

Original 28.5 kB
After minification 26.1 kB
After compression 20.1 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 8.5 kB or 30% of the original size.

CSS Optimization

-89%

Potential reduce by 31.5 kB

Original 35.6 kB
After minification 22.3 kB
After compression 4.1 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. Fiskebat.no needs all CSS files to be minified and compressed as it can save up to 31.5 kB or 89% of the original size.

Requests Now

108

After Optimization

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

[id] attributes on active, focusable elements are not unique

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

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

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

Language and Encoding

Language Detected

NO
Language Claimed

NB
Encoding

ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fiskebat.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it does not match the claimed language. Our system also found out that Fiskebat.no main page’s claimed encoding is iso-8859-1. 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

fiskebat.no

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Fiskebåt

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

fiskebat.no

ofj4ncw.js

StyleSheet.css

Custom.css

JScript.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

fiskebat.no

ofj4ncw.js

StyleSheet.css

Custom.css

JScript.js

javascript.js

standard.css

custom_mod2.css

15

ga.js

body_bg.png

header_logo_2013.png

header_icon_rss.png

header_icon_twitter.png

header_icon_linkedin.png

header_icon_facebook.png

topsearch_img_btn.png

toolTip_mobile.png

toolTip_map.png

toolTip_print.png

toolTip_txtsize_neg.png

toolTip_txtsize_pos.png

620_BffFibEJdd1.jpg

300_bfFfiAdhdi1.jpg

300_bffFhdeDdh1.jpg

220_bfFfhBieDA1.jpg

300_BffFgfAIif1.jpeg

300_BFfFFECCDG1.jpg

220_bFFfEHbaHE1.jpg

300_bfFfbCiijI1.jpeg

300_BFfFBCBFJH1.jpg

220_BFFfBBHbEC1.jpg

300_BFfFBaJIHI1.jpg

300_bfffadfGcc1.jpg

220_BffFadHFga1.jpg

300_bffEjebDdj1.jpg

300_BffEifCIjd1.jpg

220_BFFeIFCdIC1.jpg

300_BFfEGaJCGF1.png

300_BFfEgaFEbj1.jpg

220_BFfEFcGGCJ1.jpg

content_right_icon_calendar.png

icn_cal_right_column.png