Tools & Wizards About Us
iqos.dk screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

iqos.dk

IQOS.com – Heated Tobacco Store

Page Load Speed

4 sec in total

First Response

247 ms

Resources Loaded

3.6 sec

Page Rendered

163 ms

iqos.dk screenshot

About Website

Visit iqos.dk now to see the best up-to-date IQOS content and also check out these interesting facts you probably never knew about iqos.dk

Welcome to our heated tobacco store. Visit the shop, exploure our variety of services or contact our experts to get help and guidance on our products.

Visit iqos.dk

Key Findings

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

Performance Metrics

iqos.dk performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value800 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0.134

80/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

iqos.dk

247 ms

iqos.dk

292 ms

en

433 ms

otSDKStub.js

52 ms

standalone.6ea53f248c19e20cc07f661c97dfdab095d9eb4427cb268ea01e5cfe545a9db71729762746.css

339 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Iqos.dk, 54% (22 requests) were made to D133apvw5ab1lf.cloudfront.net and 22% (9 requests) were made to D414p9b9qvasy.cloudfront.net. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source D414p9b9qvasy.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 549.2 kB (13%)

Content Size

4.1 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Iqos.dk main page is 4.1 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. 65% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 160.1 kB

  • Original 195.3 kB
  • After minification 170.4 kB
  • After compression 35.1 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 24.9 kB, which is 13% 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 160.1 kB or 82% of the original size.

Image Optimization

-11%

Potential reduce by 385.5 kB

  • Original 3.4 MB
  • After minification 3.0 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. Obviously, IQOS needs image optimization as it can save up to 385.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 1.7 kB

  • Original 329.7 kB
  • After minification 329.7 kB
  • After compression 327.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 1.8 kB

  • Original 197.9 kB
  • After minification 197.9 kB
  • After compression 196.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. Iqos.dk has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 9 (26%)

Requests Now

34

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

iqos.dk

iqos.dk

247 ms

iqos.dk

iqos.dk

292 ms

en

en

433 ms

otSDKStub.js

otSDKStub.js

52 ms

standalone.6ea53f248c19e20cc07f661c97dfdab095d9eb4427cb268ea01e5cfe545a9db71729762746.css

standalone.6ea53f248c19e20cc07f661c97dfdab095d9eb4427cb268ea01e5cfe545a9db71729762746.css

339 ms

scripts-d05aeb4ccd28409713d340f7b4572d213b05576af5bf648b7d8cf4fa86ef0cae1729762746.js

scripts-d05aeb4ccd28409713d340f7b4572d213b05576af5bf648b7d8cf4fa86ef0cae1729762746.js

414 ms

ecommerce.js

ecommerce.js

88 ms

googletags.js

googletags.js

163 ms

font-awesome.min.css

font-awesome.min.css

44 ms

countdown.min.js

countdown.min.js

458 ms

cpagent142456.js

cpagent142456.js

137 ms

5VFdqCMx_N0%3D

5VFdqCMx_N0%3D

51 ms

delivery-icon.svg

delivery-icon.svg

412 ms

chevron-up-small.svg

chevron-up-small.svg

73 ms

1-logo-1-1-iqos-dark-word.png

1-logo-1-1-iqos-dark-word.png

74 ms

icons-24-location-light-theme-1.svg

icons-24-location-light-theme-1.svg

84 ms

ico-user-slate.svg

ico-user-slate.svg

162 ms

cart-slate.svg

cart-slate.svg

279 ms

home_banner_1_hero_desktop.png

home_banner_1_hero_desktop.png

1564 ms

guy_smiling_sofa.png

guy_smiling_sofa.png

1131 ms

iqos-heated-tobacco-myservices-d.jpg

iqos-heated-tobacco-myservices-d.jpg

1227 ms

heat_and_brew_store_copenhagen.png

heat_and_brew_store_copenhagen.png

1569 ms

return-icon.svg

return-icon.svg

508 ms

iqos-mbg-navbanner_1.gif

iqos-mbg-navbanner_1.gif

538 ms

60_days_EN.gif

60_days_EN.gif

535 ms

IQOSW04-Regular.woff

IQOSW04-Regular.woff

237 ms

IQOSW04-Light.woff

IQOSW04-Light.woff

264 ms

IQOSW04-Bold.woff

IQOSW04-Bold.woff

1304 ms

NeoSansPanEu-Regular-v11.woff

NeoSansPanEu-Regular-v11.woff

234 ms

mbg_stamp_en.gif

mbg_stamp_en.gif

186 ms

trio_banner_color.gif

trio_banner_color.gif

205 ms

a-woman-comparing-her-iqos-device.jpg

a-woman-comparing-her-iqos-device.jpg

1171 ms

Contact_icons_footer.svg

Contact_icons_footer.svg

372 ms

support_sprite.png

support_sprite.png

1590 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

44 ms

DK_shipping_icons.png

DK_shipping_icons.png

1457 ms

payment_options_sprite.png

payment_options_sprite.png

1458 ms

Visa_white_2021.png

Visa_white_2021.png

1505 ms

viabill-primary-logo-color-O5E.png

viabill-primary-logo-color-O5E.png

1171 ms

scripts-f08235a0d71f24ca96f8a8210be9ea51db4aec5a10f5feca7f6ca5e0618786b31729762746.js

scripts-f08235a0d71f24ca96f8a8210be9ea51db4aec5a10f5feca7f6ca5e0618786b31729762746.js

846 ms

scripts-a572eb2b5da190c8fe0a797a26b75ec43280699912af388f0cde8fab3bccad211729762746.js

scripts-a572eb2b5da190c8fe0a797a26b75ec43280699912af388f0cde8fab3bccad211729762746.js

20 ms

Accessibility Review

iqos.dk accessibility score

89

Accessibility Issues

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

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

iqos.dk best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the notification permission on page load

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

Missing source maps for large first-party JavaScript

SEO Factors

iqos.dk SEO score

86

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

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iqos.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 Iqos.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

iqos.dk

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