Tools & Wizards About Us
dataroam.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

dataroam.com

Dataroam - Use your phone abroad with a Dataroam SIM card

Page Load Speed

6.3 sec in total

First Response

1.3 sec

Resources Loaded

4.9 sec

Page Rendered

84 ms

dataroam.com screenshot

About Website

Click here to check amazing Dataroam content. Otherwise, check out these important facts you probably never knew about dataroam.com

Dataroam will connect to local Europe networks at 4G speeds, making it one of the fastest, and most secure options for mobile data available today.

Visit dataroam.com

Key Findings

We analyzed Dataroam.com page load time and found that the first response time was 1.3 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

dataroam.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value18.7 s

0/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value1,080 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

Network Requests Diagram

dataroam.com

1297 ms

www.dataroam.com

1317 ms

rbw3ysx.css

97 ms

css

95 ms

css

355 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 77% of them (82 requests) were addressed to the original Dataroam.com, 14% (15 requests) were made to Use.typekit.net and 2% (2 requests) were made to Css.zohocdn.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Dataroam.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 142.0 kB (6%)

Content Size

2.3 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dataroam.com main page is 2.3 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 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 66.9 kB

  • Original 77.8 kB
  • After minification 56.9 kB
  • After compression 10.9 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 20.9 kB, which is 27% 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 66.9 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 28.5 kB

  • Original 2.0 MB
  • After minification 2.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. Dataroam images are well optimized though.

JavaScript Optimization

-29%

Potential reduce by 46.7 kB

  • Original 160.0 kB
  • After minification 159.6 kB
  • After compression 113.3 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 46.7 kB or 29% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 5 B

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.

Requests Breakdown

Number of requests can be reduced by 44 (49%)

Requests Now

89

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dataroam.com

dataroam.com

1297 ms

www.dataroam.com

www.dataroam.com

1317 ms

rbw3ysx.css

rbw3ysx.css

97 ms

css

css

95 ms

css

css

355 ms

css

css

272 ms

css

css

427 ms

modernizr

modernizr

271 ms

jquery

jquery

474 ms

bootstrap

bootstrap

343 ms

owl.carousel.js

owl.carousel.js

485 ms

navigation.js

navigation.js

399 ms

0b733b7816.js

0b733b7816.js

64 ms

angular

angular

596 ms

app

app

490 ms

js

js

79 ms

greensock.js

greensock.js

710 ms

layerslider.transitions.js

layerslider.transitions.js

510 ms

layerslider.kreaturamedia.jquery.js

layerslider.kreaturamedia.jquery.js

708 ms

pause.js

pause.js

527 ms

main.js

main.js

528 ms

cookie-policy.js

cookie-policy.js

592 ms

p.css

p.css

26 ms

fbevents.js

fbevents.js

103 ms

widget

widget

598 ms

dataroam.svg

dataroam.svg

100 ms

dataroam-usa.jpg

dataroam-usa.jpg

563 ms

esim-card.svg

esim-card.svg

103 ms

device.png

device.png

326 ms

dataroam-sim-shadow.png

dataroam-sim-shadow.png

302 ms

italy.svg

italy.svg

98 ms

united-kingdom.svg

united-kingdom.svg

301 ms

france.svg

france.svg

302 ms

spain.svg

spain.svg

299 ms

portugal.svg

portugal.svg

396 ms

ireland.svg

ireland.svg

385 ms

germany.svg

germany.svg

397 ms

austria.svg

austria.svg

393 ms

netherlands.svg

netherlands.svg

384 ms

greece.svg

greece.svg

468 ms

andorra.svg

andorra.svg

473 ms

azores.svg

azores.svg

471 ms

belgium.svg

belgium.svg

470 ms

bulgaria.svg

bulgaria.svg

470 ms

canary-islands.svg

canary-islands.svg

557 ms

croatia.svg

croatia.svg

554 ms

cyprus.png

cyprus.png

558 ms

czech-republic.svg

czech-republic.svg

557 ms

denmark.svg

denmark.svg

553 ms

estonia.svg

estonia.svg

638 ms

finland.svg

finland.svg

636 ms

gibraltar.svg

gibraltar.svg

639 ms

guernsey.svg

guernsey.svg

640 ms

hungary.svg

hungary.svg

641 ms

iceland.svg

iceland.svg

642 ms

isle-of-man.svg

isle-of-man.svg

726 ms

jersey.svg

jersey.svg

723 ms

latvia.svg

latvia.svg

721 ms

liechtenstein.svg

liechtenstein.svg

654 ms

lithuania.svg

lithuania.svg

647 ms

d

d

208 ms

d

d

231 ms

d

d

235 ms

d

d

232 ms

d

d

232 ms

d

d

233 ms

d

d

234 ms

d

d

232 ms

d

d

235 ms

d

d

233 ms

d

d

234 ms

d

d

235 ms

d

d

235 ms

d

d

236 ms

luxembourg.svg

luxembourg.svg

629 ms

madeira.svg

madeira.svg

706 ms

malta.svg

malta.svg

706 ms

monaco.svg

monaco.svg

597 ms

norway.svg

norway.svg

509 ms

poland.svg

poland.svg

511 ms

romania.svg

romania.svg

511 ms

san-marino.svg

san-marino.svg

570 ms

slovakia.svg

slovakia.svg

566 ms

slovenia.svg

slovenia.svg

505 ms

sweden.svg

sweden.svg

499 ms

switzerland.svg

switzerland.svg

505 ms

onetreeplanted-white.png

onetreeplanted-white.png

503 ms

dataroam-loading.gif

dataroam-loading.gif

586 ms

speed.svg

speed.svg

507 ms

cost.svg

cost.svg

518 ms

devices.svg

devices.svg

530 ms

otp-proud-partner.svg

otp-proud-partner.svg

671 ms

dataroam-sim.svg

dataroam-sim.svg

598 ms

wedge-pink.svg

wedge-pink.svg

513 ms

dataroam.svg

dataroam.svg

514 ms

wedge-blue.svg

wedge-blue.svg

519 ms

dataroam-wifi-hotspot.png

dataroam-wifi-hotspot.png

540 ms

onetreeplanted.png

onetreeplanted.png

591 ms

tree.png

tree.png

598 ms

website

website

325 ms

little-dots.svg

little-dots.svg

517 ms

people-airport.jpg

people-airport.jpg

633 ms

happy-family.jpg

happy-family.jpg

636 ms

floatbutton1_0uA5KIDjSJBNGPeiRDI3YtNcjWJ9mZsPq48NM5iMzp7_jWYVkIHbMtgrDX_xil60_.css

floatbutton1_0uA5KIDjSJBNGPeiRDI3YtNcjWJ9mZsPq48NM5iMzp7_jWYVkIHbMtgrDX_xil60_.css

100 ms

floatbutton1_gagAduz5tiLSaBz7XRSC6p-M4kbireaUx12UCBqdoxV8brFf-iczAg0VKg-2ght8_.js

floatbutton1_gagAduz5tiLSaBz7XRSC6p-M4kbireaUx12UCBqdoxV8brFf-iczAg0VKg-2ght8_.js

142 ms

siq_mpWsf52LIPg9mU40fjRdjF6WMUs-Q0VNu4KH07GkhNZGQTRxW2eRyFJLAq9VKCYB_.ttf

siq_mpWsf52LIPg9mU40fjRdjF6WMUs-Q0VNu4KH07GkhNZGQTRxW2eRyFJLAq9VKCYB_.ttf

23 ms

Accessibility Review

dataroam.com accessibility score

74

Accessibility Issues

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

dataroam.com best practices score

67

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

dataroam.com SEO score

83

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dataroam.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Dataroam.com 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

dataroam.com

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