Tools & Wizards About Us
pl.mycall.no screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    79% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

pl.mycall.no

Tanie połączenia do Polski – Abonamenty od 99,- Karta SIM bez D-numeru | Mycall

Page Load Speed

3.8 sec in total

First Response

879 ms

Resources Loaded

2.8 sec

Page Rendered

130 ms

pl.mycall.no screenshot

About Website

Click here to check amazing Pl Mycall content for Norway. Otherwise, check out these important facts you probably never knew about pl.mycall.no

Z Mycall otrzymujesz nielimitowane połączenia do Polski, UE, Wielkiej Brytanii, USA oraz Kanady z pakietem danych nawet do 50GB. Bez konieczności sprawdzania zdolności kredytowej czy podpisywania umow...

Visit pl.mycall.no

Key Findings

We analyzed Pl.mycall.no page load time and found that the first response time was 879 ms and then it took 2.9 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

pl.mycall.no performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

58/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

18/100

25%

SI (Speed Index)

Value4.4 s

75/100

10%

TBT (Total Blocking Time)

Value240 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value6.5 s

59/100

10%

Network Requests Diagram

mycall.no

879 ms

jquery-ui.min.css

345 ms

bootstrap.min.css

452 ms

bootstrap-responsive.min.css

371 ms

bootstrap-select.min.css

368 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Pl.mycall.no, 14% (5 requests) were made to Mycall.no and 6% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (879 ms) relates to the external source Mycall.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 233.5 kB (49%)

Content Size

479.6 kB

After Optimization

246.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pl.mycall.no main page is 479.6 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. 25% of websites need less resources to load. CSS take 208.1 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 10.9 kB

  • Original 15.4 kB
  • After minification 14.2 kB
  • After compression 4.5 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.9 kB or 71% of the original size.

Image Optimization

-14%

Potential reduce by 28.4 kB

  • Original 205.0 kB
  • After minification 176.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, Pl Mycall needs image optimization as it can save up to 28.4 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-43%

Potential reduce by 22.2 kB

  • Original 51.1 kB
  • After minification 50.6 kB
  • After compression 28.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 22.2 kB or 43% of the original size.

CSS Optimization

-83%

Potential reduce by 172.0 kB

  • Original 208.1 kB
  • After minification 196.4 kB
  • After compression 36.0 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. Pl.mycall.no needs all CSS files to be minified and compressed as it can save up to 172.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (32%)

Requests Now

31

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mycall.no

mycall.no

879 ms

jquery-ui.min.css

jquery-ui.min.css

345 ms

bootstrap.min.css

bootstrap.min.css

452 ms

bootstrap-responsive.min.css

bootstrap-responsive.min.css

371 ms

bootstrap-select.min.css

bootstrap-select.min.css

368 ms

style.css

style.css

472 ms

jquery.min.js

jquery.min.js

74 ms

jquery-ui.min.js

jquery-ui.min.js

104 ms

bootstrap.min.js

bootstrap.min.js

38 ms

common.js

common.js

684 ms

cookie.js

cookie.js

355 ms

gtm.js

gtm.js

127 ms

no.png

no.png

110 ms

mycall.no

mycall.no

777 ms

en.png

en.png

103 ms

pl.png

pl.png

104 ms

logo.png

logo.png

106 ms

glyphicons-halflings.png

glyphicons-halflings.png

265 ms

mypages.png

mypages.png

222 ms

0316-Roaming-NO.jpg

0316-Roaming-NO.jpg

356 ms

6GB-datapakke-no-en.jpg

6GB-datapakke-no-en.jpg

274 ms

activate.png

activate.png

275 ms

mms-data.png

mms-data.png

284 ms

1015-MyCall-mins-NO.jpg

1015-MyCall-mins-NO.jpg

430 ms

0216-PreOwned-iPhone-SB-NO.jpg

0216-PreOwned-iPhone-SB-NO.jpg

482 ms

fb.png

fb.png

380 ms

tvitter-ikon.png

tvitter-ikon.png

364 ms

linkedin.png

linkedin.png

373 ms

youtube.png

youtube.png

444 ms

support_phone.png

support_phone.png

450 ms

chevinpro-bold.woff

chevinpro-bold.woff

589 ms

analytics.js

analytics.js

47 ms

collect

collect

37 ms

collect

collect

62 ms

ga-audiences

ga-audiences

42 ms

Accessibility Review

pl.mycall.no accessibility score

80

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

High

[aria-*] attributes do not have valid values

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

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

Best Practices

pl.mycall.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

High

Missing source maps for large first-party JavaScript

SEO Factors

pl.mycall.no SEO score

93

Search Engine Optimization Advices

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

    PL

  • Language Claimed

    NO

  • Encoding

    UTF-8

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

pl.mycall.no

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