Tools & Wizards About Us
phoneshark.com screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    59% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

phoneshark.com

International Prepaid Calling Cards & Plans | Enjoy Prepaid

Page Load Speed

959 ms in total

First Response

352 ms

Resources Loaded

494 ms

Page Rendered

113 ms

phoneshark.com screenshot

About Website

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

Choose an International Calling Card from Enjoy Prepaid and you can expect: Low international calling rates, great quality, instant PIN delivery and 24/7 customer service in several languages.

Visit phoneshark.com

Key Findings

We analyzed Phoneshark.com page load time and found that the first response time was 352 ms and then it took 607 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

phoneshark.com performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value5.0 s

62/100

10%

TBT (Total Blocking Time)

Value690 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.086

93/100

15%

TTI (Time to Interactive)

Value9.7 s

29/100

10%

Network Requests Diagram

phoneshark.com

352 ms

fonts.css

172 ms

question_mark.gif

112 ms

phoneshark_logo_since1999.JPG

149 ms

credit_cards_4.gif

151 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 92% of them (24 requests) were addressed to the original Phoneshark.com, 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (352 ms) belongs to the original domain Phoneshark.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 89.3 kB (62%)

Content Size

144.2 kB

After Optimization

54.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Phoneshark.com main page is 144.2 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. Only 5% of websites need less resources to load. HTML takes 91.6 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 83.0 kB

  • Original 91.6 kB
  • After minification 84.1 kB
  • After compression 8.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 83.0 kB or 91% of the original size.

Image Optimization

-2%

Potential reduce by 789 B

  • Original 40.5 kB
  • After minification 39.8 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. Phoneshark images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 971 B

  • Original 6.8 kB
  • After minification 6.8 kB
  • After compression 5.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 971 B or 14% of the original size.

CSS Optimization

-86%

Potential reduce by 4.5 kB

  • Original 5.2 kB
  • After minification 3.9 kB
  • After compression 729 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. Phoneshark.com needs all CSS files to be minified and compressed as it can save up to 4.5 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (52%)

Requests Now

25

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

phoneshark.com

phoneshark.com

352 ms

fonts.css

fonts.css

172 ms

question_mark.gif

question_mark.gif

112 ms

phoneshark_logo_since1999.JPG

phoneshark_logo_since1999.JPG

149 ms

credit_cards_4.gif

credit_cards_4.gif

151 ms

paypal_logo_small.gif

paypal_logo_small.gif

96 ms

GoogleCheckout%2068x26.jpg

GoogleCheckout%2068x26.jpg

82 ms

urchin.js

urchin.js

35 ms

PH-Flag-Thumbnail.gif

PH-Flag-Thumbnail.gif

29 ms

US-Flag-Thumbnail.gif

US-Flag-Thumbnail.gif

54 ms

GH-Flag-Thumbnail.gif

GH-Flag-Thumbnail.gif

43 ms

RU-Flag-Thumbnail.gif

RU-Flag-Thumbnail.gif

30 ms

SA-Flag-Thumbnail.gif

SA-Flag-Thumbnail.gif

30 ms

IR-Flag-Thumbnail.gif

IR-Flag-Thumbnail.gif

33 ms

LK-Flag-Thumbnail.gif

LK-Flag-Thumbnail.gif

51 ms

SG-Flag-Thumbnail.gif

SG-Flag-Thumbnail.gif

52 ms

GR-Flag-Thumbnail.gif

GR-Flag-Thumbnail.gif

56 ms

NO-Flag-Thumbnail.gif

NO-Flag-Thumbnail.gif

69 ms

MX-Flag-Thumbnail.gif

MX-Flag-Thumbnail.gif

70 ms

NZ-Flag-Thumbnail.gif

NZ-Flag-Thumbnail.gif

73 ms

wireless_carriers.gif

wireless_carriers.gif

77 ms

Prepaid_phonecards.JPG

Prepaid_phonecards.JPG

87 ms

example_phonecard.jpg

example_phonecard.jpg

142 ms

Satisfaction_Guaranteed.gif

Satisfaction_Guaranteed.gif

104 ms

McAfee%20SiteAdvisor.gif

McAfee%20SiteAdvisor.gif

95 ms

__utm.gif

__utm.gif

10 ms

Accessibility Review

phoneshark.com accessibility score

70

Accessibility Issues

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

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

Form elements do not have associated labels

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

phoneshark.com best practices score

75

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

Browser errors were logged to the console

SEO Factors

phoneshark.com SEO score

98

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phoneshark.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 Phoneshark.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

phoneshark.com

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