Tools & Wizards About Us
ices.dk screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

ices.dk

Welcome to ICES

Page Load Speed

7.4 sec in total

First Response

561 ms

Resources Loaded

6.7 sec

Page Rendered

205 ms

ices.dk screenshot

About Website

Welcome to ices.dk homepage info - get ready to check ICES best content for Russia right away, or after learning these important things about ices.dk

International Council for the Exploration of the Sea

Visit ices.dk

Key Findings

We analyzed Ices.dk page load time and found that the first response time was 561 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

ices.dk performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value17.3 s

0/100

10%

TBT (Total Blocking Time)

Value320 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0.192

64/100

15%

TTI (Time to Interactive)

Value12.7 s

13/100

10%

Network Requests Diagram

ices.dk

561 ms

default.aspx

1207 ms

pagelayouts15.css

334 ms

corev15.css

953 ms

controls15.css

480 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 95% of them (52 requests) were addressed to the original Ices.dk, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Ices.dk.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (41%)

Content Size

2.8 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ices.dk main page is 2.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 79.4 kB

  • Original 98.8 kB
  • After minification 84.3 kB
  • After compression 19.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. This page needs HTML code to be minified as it can gain 14.5 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 79.4 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 34.6 kB

  • Original 1.4 MB
  • After minification 1.3 MB

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. ICES images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 725.8 kB

  • Original 993.3 kB
  • After minification 967.8 kB
  • After compression 267.5 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 725.8 kB or 73% of the original size.

CSS Optimization

-87%

Potential reduce by 339.3 kB

  • Original 389.4 kB
  • After minification 279.3 kB
  • After compression 50.0 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. Ices.dk needs all CSS files to be minified and compressed as it can save up to 339.3 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (68%)

Requests Now

53

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ices.dk

ices.dk

561 ms

default.aspx

default.aspx

1207 ms

pagelayouts15.css

pagelayouts15.css

334 ms

corev15.css

corev15.css

953 ms

controls15.css

controls15.css

480 ms

ICESPrint.css

ICESPrint.css

517 ms

init.js

init.js

853 ms

ScriptResource.axd

ScriptResource.axd

803 ms

blank.js

blank.js

477 ms

ScriptResource.axd

ScriptResource.axd

648 ms

jquery.min.js

jquery.min.js

37 ms

icesfunctions.js

icesfunctions.js

661 ms

ices.css

ices.css

652 ms

WebResource.axd

WebResource.axd

652 ms

ICESTheme.css

ICESTheme.css

697 ms

nivo-slider.css

nivo-slider.css

698 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

697 ms

analytics.js

analytics.js

26 ms

iceslogo.png

iceslogo.png

177 ms

favicon.ico

favicon.ico

190 ms

spcommon.png

spcommon.png

342 ms

searchresultui.png

searchresultui.png

179 ms

aquaculture_fotolia_slider.jpg

aquaculture_fotolia_slider.jpg

2928 ms

Moens_klint.jpg

Moens_klint.jpg

3368 ms

Training.jpg

Training.jpg

3120 ms

JNCC_Anton%20Dohrn.jpg

JNCC_Anton%20Dohrn.jpg

1991 ms

Riga-panorama.jpg

Riga-panorama.jpg

359 ms

rss.gif

rss.gif

502 ms

alamy%20DKH8TW%20lowest%20res%20(00000002).jpg

alamy%20DKH8TW%20lowest%20res%20(00000002).jpg

519 ms

newslettericon.png

newslettericon.png

651 ms

linkedinicon.png

linkedinicon.png

672 ms

facebookicon.png

facebookicon.png

825 ms

twittericon.png

twittericon.png

843 ms

youtubeicon.png

youtubeicon.png

999 ms

iceslogo.png

iceslogo.png

489 ms

collect

collect

32 ms

gutterbg.png

gutterbg.png

985 ms

icesddtoparrow.png

icesddtoparrow.png

1111 ms

calltoaction.png

calltoaction.png

1244 ms

newsdot.png

newsdot.png

1253 ms

opacitycampaign.png

opacitycampaign.png

1379 ms

footerlinkarrow.png

footerlinkarrow.png

1387 ms

whitedot.png

whitedot.png

1545 ms

footergradient.png

footergradient.png

1551 ms

initstrings.js

initstrings.js

1709 ms

sp.init.js

sp.init.js

1716 ms

strings.js

strings.js

292 ms

core.js

core.js

314 ms

ScriptResx.ashx

ScriptResx.ashx

169 ms

corev15.css

corev15.css

316 ms

mediaplayer.js

mediaplayer.js

156 ms

sp.core.js

sp.core.js

147 ms

default.aspx

default.aspx

957 ms

opacityslider.png

opacityslider.png

153 ms

slidearrows.png

slidearrows.png

149 ms

Accessibility Review

ices.dk accessibility score

78

Accessibility Issues

ARIA

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.

Impact

Issue

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.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

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

ices.dk best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

ices.dk SEO score

75

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

Mobile Friendly

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

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ices.dk can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Ices.dk main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

ices.dk

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