Tools & Wizards About Us
112ink.no screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

112ink.no

Miljøvennlige blekkpatroner og toner | 112ink

Page Load Speed

3 sec in total

First Response

352 ms

Resources Loaded

2.5 sec

Page Rendered

169 ms

112ink.no screenshot

About Website

Welcome to 112ink.no homepage info - get ready to check 112 Ink best content right away, or after learning these important things about 112ink.no

Kjøp miljøvennlige blekkpatroner og toner med klimasmarte leveranser. Velg grønne varer fra vårt miljøvennlige kontorutvalg. Miljøsertifiseringer.

Visit 112ink.no

Key Findings

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

Performance Metrics

112ink.no performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value2,960 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.315

37/100

15%

TTI (Time to Interactive)

Value14.5 s

8/100

10%

Network Requests Diagram

352 ms

dtagent56_bxjnpr3t_5802.js

439 ms

jquery.colorbox-1.3.16.css

339 ms

screen.css

341 ms

common.css

453 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original 112ink.no, 72% (34 requests) were made to Cdnprod.112ink.se and 9% (4 requests) were made to Config1.veinteractive.com. The less responsive or slowest element that took the longest time to load (894 ms) relates to the external source Cdnprod.112ink.se.

Page Optimization Overview & Recommendations

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

Content Size

1.7 MB

After Optimization

545.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 112ink.no main page is 1.7 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. 30% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 56.8 kB

  • Original 70.6 kB
  • After minification 65.9 kB
  • After compression 13.8 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 56.8 kB or 80% of the original size.

Image Optimization

-18%

Potential reduce by 41.7 kB

  • Original 227.3 kB
  • After minification 185.6 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, 112 Ink needs image optimization as it can save up to 41.7 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-75%

Potential reduce by 905.7 kB

  • Original 1.2 MB
  • After minification 948.6 kB
  • After compression 309.8 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 905.7 kB or 75% of the original size.

CSS Optimization

-84%

Potential reduce by 197.2 kB

  • Original 233.5 kB
  • After minification 187.0 kB
  • After compression 36.4 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. 112ink.no needs all CSS files to be minified and compressed as it can save up to 197.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (55%)

Requests Now

44

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

352 ms

dtagent56_bxjnpr3t_5802.js

dtagent56_bxjnpr3t_5802.js

439 ms

jquery.colorbox-1.3.16.css

jquery.colorbox-1.3.16.css

339 ms

screen.css

screen.css

341 ms

common.css

common.css

453 ms

changes.css

changes.css

678 ms

theme.css

theme.css

473 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

693 ms

jquery.ba-postmessage.min.js

jquery.ba-postmessage.min.js

243 ms

sitelibs.min.js

sitelibs.min.js

894 ms

site.js

site.js

564 ms

conversion.js

conversion.js

16 ms

tag.js

tag.js

118 ms

ga.js

ga.js

42 ms

cart.png

cart.png

115 ms

fold-out-minicart.png

fold-out-minicart.png

112 ms

logo-small.png

logo-small.png

123 ms

flags.png

flags.png

229 ms

fold-out.png

fold-out.png

164 ms

megaphone-112-icon.png

megaphone-112-icon.png

223 ms

binder.png

binder.png

227 ms

8805563236382.png

8805563236382.png

240 ms

search-btn.png

search-btn.png

275 ms

8987031437342.jpg

8987031437342.jpg

776 ms

8798663376926.jpg

8798663376926.jpg

340 ms

8798499012638.jpg

8798499012638.jpg

348 ms

8798499209246.jpg

8798499209246.jpg

363 ms

8798499405854.jpg

8798499405854.jpg

424 ms

8817381834782.jpg

8817381834782.jpg

605 ms

icon-instock.png

icon-instock.png

461 ms

8876946817054.jpg

8876946817054.jpg

631 ms

8876754534430.jpg

8876754534430.jpg

512 ms

8877481099294.jpg

8877481099294.jpg

511 ms

8877481394206.jpg

8877481394206.jpg

698 ms

8875980357662.jpg

8875980357662.jpg

636 ms

__utm.gif

__utm.gif

26 ms

collect

collect

64 ms

53 ms

bat.js

bat.js

83 ms

overlay.png

overlay.png

163 ms

checkbox.png

checkbox.png

260 ms

select-arrow-white.png

select-arrow-white.png

272 ms

capture-apps-4.6.0.js

capture-apps-4.6.0.js

7 ms

47 ms

iframeStorage.html

iframeStorage.html

144 ms

iframeStorage.js

iframeStorage.js

4 ms

print.css

print.css

114 ms

Accessibility Review

112ink.no accessibility score

68

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-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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.

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

112ink.no best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

112ink.no SEO score

82

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

    NO

  • Language Claimed

    NO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 112ink.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it matches the claimed language. Our system also found out that 112ink.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

112ink.no

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