Tools & Wizards About Us
vitawater.no screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

vitawater.no

WATERWELL ™ - Vann med kullsyre og smak for arbeidsplassen

Page Load Speed

5 sec in total

First Response

312 ms

Resources Loaded

4 sec

Page Rendered

632 ms

vitawater.no screenshot

About Website

Click here to check amazing Vitawater content. Otherwise, check out these important facts you probably never knew about vitawater.no

Waterwell leverer den beste løsningen for vann på arbeidsplassen. Vi tilbyr et smakfullt og sunt alternativ til dagens flaskevann og leskedrikker.

Visit vitawater.no

Key Findings

We analyzed Vitawater.no page load time and found that the first response time was 312 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

vitawater.no performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value14.7 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value4,420 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.28

43/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

vitawater.no

312 ms

waterwell.no

653 ms

wp-emoji-release.min.js

167 ms

style.css

186 ms

responsive.css

183 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Vitawater.no, 49% (25 requests) were made to Waterwell.no and 16% (8 requests) were made to Scontent.cdninstagram.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Snapwidget.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 412.1 kB (17%)

Content Size

2.4 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vitawater.no main page is 2.4 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. 45% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 10.2 kB

  • Original 14.2 kB
  • After minification 13.2 kB
  • After compression 4.0 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 10.2 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 8.6 kB

  • Original 1.8 MB
  • After minification 1.8 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. Vitawater images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 234.2 kB

  • Original 364.8 kB
  • After minification 361.9 kB
  • After compression 130.6 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 234.2 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 159.1 kB

  • Original 190.7 kB
  • After minification 168.9 kB
  • After compression 31.5 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. Vitawater.no needs all CSS files to be minified and compressed as it can save up to 159.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (51%)

Requests Now

43

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vitawater.no

vitawater.no

312 ms

waterwell.no

waterwell.no

653 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

167 ms

style.css

style.css

186 ms

responsive.css

responsive.css

183 ms

style.css

style.css

172 ms

jquery.js

jquery.js

250 ms

jquery-migrate.min.js

jquery-migrate.min.js

181 ms

responsive-modernizr.min.js

responsive-modernizr.min.js

265 ms

css

css

67 ms

custom.js

custom.js

273 ms

snapwidget.js

snapwidget.js

6 ms

responsive-scripts.min.js

responsive-scripts.min.js

279 ms

jquery.placeholder.min.js

jquery.placeholder.min.js

280 ms

wp-embed.min.js

wp-embed.min.js

306 ms

menu_ic1.png

menu_ic1.png

93 ms

soc_ic.png

soc_ic.png

93 ms

logo_mob.png

logo_mob.png

93 ms

explore_bottles.jpg

explore_bottles.jpg

415 ms

expl_concept.jpg

expl_concept.jpg

813 ms

video_bg.jpg

video_bg.jpg

769 ms

play_btn.png

play_btn.png

174 ms

need_water.jpg

need_water.jpg

579 ms

app_back.jpg

app_back.jpg

254 ms

app.png

app.png

736 ms

app_store.png

app_store.png

337 ms

play_store.png

play_store.png

420 ms

instagram_title.png

instagram_title.png

496 ms

2414 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

67 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

77 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

87 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

94 ms

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

94 ms

zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf

zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf

94 ms

combined.css

combined.css

11 ms

smoothDivScroll.css

smoothDivScroll.css

5 ms

iframeresize.js

iframeresize.js

6 ms

jquery.min.js

jquery.min.js

9 ms

analytics.js

analytics.js

21 ms

12328222_820604481401058_1401609024_n.jpg

12328222_820604481401058_1401609024_n.jpg

181 ms

12825863_848340521943462_805055896_n.jpg

12825863_848340521943462_805055896_n.jpg

177 ms

12798151_192487717792603_420853940_n.jpg

12798151_192487717792603_420853940_n.jpg

231 ms

12784095_1532335487069309_1429584900_n.jpg

12784095_1532335487069309_1429584900_n.jpg

235 ms

11363891_658935547542699_593257922_n.jpg

11363891_658935547542699_593257922_n.jpg

148 ms

12783204_711604118975913_1859356548_n.jpg

12783204_711604118975913_1859356548_n.jpg

291 ms

12798072_447936162078646_2088117329_n.jpg

12798072_447936162078646_2088117329_n.jpg

228 ms

12519608_166263113758066_1165691523_n.jpg

12519608_166263113758066_1165691523_n.jpg

233 ms

collect

collect

4 ms

collect

collect

69 ms

nr-892.min.js

nr-892.min.js

18 ms

Accessibility Review

vitawater.no accessibility score

85

Accessibility Issues

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

vitawater.no best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

vitawater.no SEO score

86

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

Language and Encoding

  • Language Detected

    NO

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vitawater.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 English language. Our system also found out that Vitawater.no 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

vitawater.no

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