Tools & Wizards About Us
iqos.ru screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

iqos.ru

IQOS Smoke-Free Alternatives to Cigarettes | Official Website

Page Load Speed

4.4 sec in total

First Response

339 ms

Resources Loaded

3.5 sec

Page Rendered

546 ms

iqos.ru screenshot

About Website

Click here to check amazing IQOS content for Russia. Otherwise, check out these important facts you probably never knew about iqos.ru

IQOS is a line of heated tobacco and electronic cigarette products. Explore our smoke-free alternatives.

Visit iqos.ru

Key Findings

We analyzed Iqos.ru page load time and found that the first response time was 339 ms and then it took 4.1 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.ru performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.037

100/100

15%

TTI (Time to Interactive)

Value5.0 s

76/100

10%

Network Requests Diagram

iqos.ru

339 ms

iqos.ru

497 ms

www.iqos.ru

615 ms

global

182 ms

iqoshtml.css

935 ms

Our browser made a total of 115 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Iqos.ru, 93% (107 requests) were made to Iqos.com and 1% (1 request) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Iqos.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 319.9 kB (47%)

Content Size

679.1 kB

After Optimization

359.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Iqos.ru main page is 679.1 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. 80% 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 270.2 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 136.9 kB

  • Original 160.6 kB
  • After minification 123.6 kB
  • After compression 23.7 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 37.1 kB, which is 23% 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 136.9 kB or 85% of the original size.

Image Optimization

-17%

Potential reduce by 44.9 kB

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

JavaScript Optimization

-56%

Potential reduce by 138.1 kB

  • Original 248.3 kB
  • After minification 247.5 kB
  • After compression 110.2 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 138.1 kB or 56% of the original size.

Requests Breakdown

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

Requests Now

107

After Optimization

85

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 107 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 13 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

iqos.ru

iqos.ru

339 ms

iqos.ru

iqos.ru

497 ms

www.iqos.ru

www.iqos.ru

615 ms

global

global

182 ms

iqoshtml.css

iqoshtml.css

935 ms

clientlib-brandworld.min.a48822ee068b64a16196e24963750428.css

clientlib-brandworld.min.a48822ee068b64a16196e24963750428.css

137 ms

clientlib-nbwiqoshtml.min.e9b350d104c8dd477e7e6b7032f26bdd.css

clientlib-nbwiqoshtml.min.e9b350d104c8dd477e7e6b7032f26bdd.css

379 ms

otSDKStub.js

otSDKStub.js

44 ms

clientlib-gtmBundle.min.98ea81ac867a844a33d79ed75015f815.js

clientlib-gtmBundle.min.98ea81ac867a844a33d79ed75015f815.js

75 ms

clientlib-akamai-get-user-location.min.da39f3725dae2d4cc779a98e655e8222.js

clientlib-akamai-get-user-location.min.da39f3725dae2d4cc779a98e655e8222.js

50 ms

clientlib-nbwFooter.min.ec15b8c0f004660e60cce1a198d92062.js

clientlib-nbwFooter.min.ec15b8c0f004660e60cce1a198d92062.js

47 ms

en.aemConfig.www.iqos.com.T1713885846107.V1628654000_224551_618_4202.json

en.aemConfig.www.iqos.com.T1713885846107.V1628654000_224551_618_4202.json

249 ms

clientlib-iqoshtml.min.d45ee5cb02e7bbd9897ae08b43a5c3f6.js

clientlib-iqoshtml.min.d45ee5cb02e7bbd9897ae08b43a5c3f6.js

87 ms

en.timeUpLocalStorageConfig.4a730225e18c2da04d374c60cca0e2d62864353cab34f9bf902990b6156d42e9.js

en.timeUpLocalStorageConfig.4a730225e18c2da04d374c60cca0e2d62864353cab34f9bf902990b6156d42e9.js

1680 ms

clientlib-ipFencingBundle.min.fb82cfd4ade9b640daea2f6698769115.js

clientlib-ipFencingBundle.min.fb82cfd4ade9b640daea2f6698769115.js

118 ms

clientlib-appBundle.min.bbef2123bbc2e21276f9bf5d51d1b7de.js

clientlib-appBundle.min.bbef2123bbc2e21276f9bf5d51d1b7de.js

249 ms

clientlib-cookies-init.min.2422f40316fc026bdd4ea42fe648f7f1.js

clientlib-cookies-init.min.2422f40316fc026bdd4ea42fe648f7f1.js

247 ms

N3CgFwEVM

N3CgFwEVM

249 ms

gtm.js

gtm.js

275 ms

P5GVK-HCJKP-8SAV5-RSGA8-VSVDN

P5GVK-HCJKP-8SAV5-RSGA8-VSVDN

275 ms

Background-global-landing-page.T1666098039368.V1628654000_224551_618_4202.jpeg

Background-global-landing-page.T1666098039368.V1628654000_224551_618_4202.jpeg

503 ms

icon-plus-black.svg

icon-plus-black.svg

204 ms

icon-minus-black.svg

icon-minus-black.svg

201 ms

flag-armenia.png

flag-armenia.png

149 ms

flag-Bahrain@3x.png

flag-Bahrain@3x.png

150 ms

flag-egypt@3x.png

flag-egypt@3x.png

152 ms

flag-israel@2x.png

flag-israel@2x.png

151 ms

flag-jordania@3x.png

flag-jordania@3x.png

180 ms

flag-kuwait@2x.png

flag-kuwait@2x.png

181 ms

flag-lebanon@3x.png

flag-lebanon@3x.png

188 ms

flag-Morocco@3x.png

flag-Morocco@3x.png

189 ms

flag-palestine@2x.png

flag-palestine@2x.png

211 ms

flag-reunion@3x.png

flag-reunion@3x.png

214 ms

flag-saudiarabia.png

flag-saudiarabia.png

224 ms

flag-southafrica.png

flag-southafrica.png

224 ms

flag-Tunisia@3x.png

flag-Tunisia@3x.png

234 ms

flag-uae@3x.png

flag-uae@3x.png

243 ms

flag-India@3x.png

flag-India@3x.png

247 ms

flag-Iraq@3x.png

flag-Iraq@3x.png

248 ms

flag-Oman@3x.png

flag-Oman@3x.png

255 ms

flag-Qatar@3x.png

flag-Qatar@3x.png

272 ms

flag-canada.png

flag-canada.png

269 ms

flag-colombia.png

flag-colombia.png

270 ms

flag-aruba@3x.png

flag-aruba@3x.png

280 ms

flag-canada@2x.png

flag-canada@2x.png

292 ms

flag-costa-rica@3x.png

flag-costa-rica@3x.png

292 ms

flag-curacao@3x.png

flag-curacao@3x.png

300 ms

flag-dominicanrepublic.png

flag-dominicanrepublic.png

305 ms

flag-equador@3x.png

flag-equador@3x.png

313 ms

flag-elsalvador@3x.png

flag-elsalvador@3x.png

314 ms

flag-grenada@3x.png

flag-grenada@3x.png

328 ms

flag-guatemala.png

flag-guatemala.png

333 ms

flag-mexico.png

flag-mexico.png

336 ms

flag-usa.png

flag-usa.png

337 ms

flag-australia.png

flag-australia.png

331 ms

IQOSW04-Bold.woff

IQOSW04-Bold.woff

277 ms

IQOSW04-Regular.woff

IQOSW04-Regular.woff

246 ms

flag-china@3x.png

flag-china@3x.png

207 ms

flag-Georgia@3x.png

flag-Georgia@3x.png

232 ms

flag-indonesia.png

flag-indonesia.png

208 ms

flag-japan.png

flag-japan.png

244 ms

flag-kazakhstan.png

flag-kazakhstan.png

238 ms

config.json

config.json

64 ms

flag-korea.png

flag-korea.png

237 ms

flag-kyrgystan@3x.png

flag-kyrgystan@3x.png

282 ms

flag-Macedonia@3x.png

flag-Macedonia@3x.png

279 ms

flag-malaysia%403x.png

flag-malaysia%403x.png

273 ms

flag-maldives.png

flag-maldives.png

269 ms

flag-moldova@2x.png

flag-moldova@2x.png

261 ms

flag-newzealand@2x.png

flag-newzealand@2x.png

262 ms

flag-philippines.png

flag-philippines.png

254 ms

flag-russia.png

flag-russia.png

245 ms

flag-taiwan.png

flag-taiwan.png

243 ms

flag-vietnam@3x.png

flag-vietnam@3x.png

242 ms

flag-Hongkong@3x.png

flag-Hongkong@3x.png

242 ms

flag-Singapore@3x.png

flag-Singapore@3x.png

232 ms

flag-albania@2x.png

flag-albania@2x.png

241 ms

flag-Austria@3x.png

flag-Austria@3x.png

240 ms

flag-bosnia.png

flag-bosnia.png

237 ms

flag-bulgaria@2x.png

flag-bulgaria@2x.png

230 ms

flag-croatia@3x.png

flag-croatia@3x.png

236 ms

flag-Cyprus@3x.png

flag-Cyprus@3x.png

235 ms

flag-czech@2x.png

flag-czech@2x.png

229 ms

flag-denmark.png

flag-denmark.png

228 ms

flag-finland@2x.png

flag-finland@2x.png

236 ms

flag-estonia@3x.png

flag-estonia@3x.png

230 ms

flag-france.png

flag-france.png

226 ms

flag-germany@2x.png

flag-germany@2x.png

224 ms

flag-greece.png

flag-greece.png

227 ms

flag-hungary.png

flag-hungary.png

223 ms

flag-italy.png

flag-italy.png

229 ms

flag-latvia@3x.png

flag-latvia@3x.png

202 ms

flag-lithuania.png

flag-lithuania.png

199 ms

flag-montenegro@3x.png

flag-montenegro@3x.png

170 ms

flag-netherlands_2.png

flag-netherlands_2.png

184 ms

flag-ncyprus@3x.png

flag-ncyprus@3x.png

186 ms

flag-poland.png

flag-poland.png

186 ms

flag-portugal.png

flag-portugal.png

133 ms

flag-romania@2x.png

flag-romania@2x.png

137 ms

flag-serbia@2x.png

flag-serbia@2x.png

153 ms

flag-slovakia.png

flag-slovakia.png

150 ms

flag-slovenia.png

flag-slovenia.png

149 ms

flag-spain.png

flag-spain.png

150 ms

flag-Sweden@3x.png

flag-Sweden@3x.png

159 ms

flag-switzerland.png

flag-switzerland.png

172 ms

flag-ukraine%403x.png

flag-ukraine%403x.png

171 ms

flag-uk.png

flag-uk.png

170 ms

flag-uzbekistan@3x.png

flag-uzbekistan@3x.png

356 ms

flag-belgium@3x.png

flag-belgium@3x.png

174 ms

flag-monaco@2x.png

flag-monaco@2x.png

184 ms

flag-turkey.png

flag-turkey.png

183 ms

flag-Ireland@3x.png

flag-Ireland@3x.png

175 ms

flag-Luxembourg@3x.png

flag-Luxembourg@3x.png

185 ms

flag-Norway@3x.png

flag-Norway@3x.png

195 ms

nr-spa-1215.min.js

nr-spa-1215.min.js

24 ms

Accessibility Review

iqos.ru accessibility score

61

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

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.

High

[aria-*] attributes do not have valid values

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

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

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

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.ru 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

SEO Factors

iqos.ru SEO score

91

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

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 Iqos.ru 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.ru 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.ru

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: