Tools & Wizards About Us
pranktexts.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

pranktexts.com

Prank Text | Send Fake Text Messages and Funny SMS with Prank Texts

Page Load Speed

2.1 sec in total

First Response

314 ms

Resources Loaded

1.7 sec

Page Rendered

162 ms

pranktexts.com screenshot

About Website

Visit pranktexts.com now to see the best up-to-date Prank Texts content and also check out these interesting facts you probably never knew about pranktexts.com

Prank Texts OFFER get 1 Free Credit! Send funny text messages to, and from any mobile in the world. You are able to spoof your friends and send them fake SMS messages!

Visit pranktexts.com

Key Findings

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

Performance Metrics

pranktexts.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value16.6 s

0/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value1,100 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.107

88/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

pranktexts.com

314 ms

www.pranktexts.com

331 ms

css

24 ms

css

43 ms

bootstrap.css

171 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 58% of them (35 requests) were addressed to the original Pranktexts.com, 12% (7 requests) were made to Fonts.gstatic.com and 8% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (771 ms) belongs to the original domain Pranktexts.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 93.9 kB (8%)

Content Size

1.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pranktexts.com main page is 1.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. 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 738.7 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 23.5 kB

  • Original 31.1 kB
  • After minification 29.0 kB
  • After compression 7.6 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 23.5 kB or 76% of the original size.

Image Optimization

-5%

Potential reduce by 36.6 kB

  • Original 738.7 kB
  • After minification 702.0 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. Prank Texts images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 33.2 kB

  • Original 270.4 kB
  • After minification 270.2 kB
  • After compression 237.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 33.2 kB or 12% of the original size.

CSS Optimization

-1%

Potential reduce by 543 B

  • Original 84.8 kB
  • After minification 84.8 kB
  • After compression 84.3 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. Pranktexts.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (29%)

Requests Now

49

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pranktexts.com

pranktexts.com

314 ms

www.pranktexts.com

www.pranktexts.com

331 ms

css

css

24 ms

css

css

43 ms

bootstrap.css

bootstrap.css

171 ms

style.css

style.css

167 ms

jquery-1-11-2.js

jquery-1-11-2.js

313 ms

bootstrap.min.js

bootstrap.min.js

169 ms

all.js

all.js

20 ms

analytics.js

analytics.js

30 ms

Vks1-Oi9-wc

Vks1-Oi9-wc

151 ms

all.js

all.js

28 ms

bg-repeat.png

bg-repeat.png

124 ms

bg.png

bg.png

710 ms

PT-logo.png

PT-logo.png

123 ms

fb-icon.png

fb-icon.png

160 ms

twitter-icon.png

twitter-icon.png

200 ms

home.png

home.png

201 ms

Pricing.png

Pricing.png

201 ms

how-its-work.png

how-its-work.png

201 ms

send-sms.png

send-sms.png

469 ms

pricing-new.png

pricing-new.png

469 ms

tell-friend.png

tell-friend.png

469 ms

HomepageV1.gif

HomepageV1.gif

469 ms

login-box-bg.png

login-box-bg.png

469 ms

new-slider-bg.png

new-slider-bg.png

543 ms

summer.png

summer.png

542 ms

how-prank-text-work.png

how-prank-text-work.png

543 ms

send-prank-text-messages.png

send-prank-text-messages.png

543 ms

funny-prank-text-messages.png

funny-prank-text-messages.png

627 ms

send-fake-text-messages.png

send-fake-text-messages.png

627 ms

prank-text-messaging.png

prank-text-messaging.png

627 ms

free-facebook-credit.png

free-facebook-credit.png

706 ms

1-box.png

1-box.png

626 ms

free.png

free.png

707 ms

2-box.png

2-box.png

707 ms

3-box-home.png

3-box-home.png

707 ms

sep-line.png

sep-line.png

706 ms

footer-bg-new.png

footer-bg-new.png

771 ms

collect

collect

109 ms

58 ms

hES06XlsOjtJsgCkx1Pkfon__Q.woff

hES06XlsOjtJsgCkx1Pkfon__Q.woff

362 ms

COMICBD_3.TTF

COMICBD_3.TTF

690 ms

CREABBB_.TTF

CREABBB_.TTF

662 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

370 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

398 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

407 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

400 ms

www-player.css

www-player.css

8 ms

www-embed-player.js

www-embed-player.js

39 ms

base.js

base.js

79 ms

js

js

294 ms

ad_status.js

ad_status.js

185 ms

om_QuI9M6WDewyV11PDqwyZXtjss-zYzBgeHLXyLCgE.js

om_QuI9M6WDewyV11PDqwyZXtjss-zYzBgeHLXyLCgE.js

125 ms

embed.js

embed.js

32 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

61 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

75 ms

Create

Create

104 ms

id

id

19 ms

GenerateIT

GenerateIT

13 ms

Accessibility Review

pranktexts.com accessibility score

86

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

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

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

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

pranktexts.com SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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 Pranktexts.com 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 Pranktexts.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

pranktexts.com

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