Tools & Wizards About Us
dirtyphones.org screenshot

Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

dirtyphones.org

dirtyphones.org - This website is for sale! - dirtyphones Resources and Information.

Page Load Speed

8 sec in total

First Response

1.8 sec

Resources Loaded

5.8 sec

Page Rendered

499 ms

dirtyphones.org screenshot

About Website

Click here to check amazing Dirtyphones content for India. Otherwise, check out these important facts you probably never knew about dirtyphones.org

This website is for sale! dirtyphones.org is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, dirtyphones.or...

Visit dirtyphones.org

Key Findings

We analyzed Dirtyphones.org page load time and found that the first response time was 1.8 sec and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

dirtyphones.org performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.0 s

100/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value1,620 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.197

62/100

15%

TTI (Time to Interactive)

Value4.3 s

84/100

10%

Network Requests Diagram

www.dirtyphones.org

1777 ms

foundation.css

1741 ms

custom_foundation.css

656 ms

layout.css

895 ms

nav_slider.css

1355 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 73% of them (54 requests) were addressed to the original Dirtyphones.org, 5% (4 requests) were made to Apis.google.com and 4% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Dirtyphones.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 970.8 kB (30%)

Content Size

3.2 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dirtyphones.org main page is 3.2 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. 50% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 60.9 kB

  • Original 81.0 kB
  • After minification 72.5 kB
  • After compression 20.1 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 60.9 kB or 75% of the original size.

Image Optimization

-6%

Potential reduce by 138.2 kB

  • Original 2.1 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. Dirtyphones images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 475.0 kB

  • Original 658.0 kB
  • After minification 577.1 kB
  • After compression 183.0 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 475.0 kB or 72% of the original size.

CSS Optimization

-91%

Potential reduce by 296.8 kB

  • Original 327.2 kB
  • After minification 252.5 kB
  • After compression 30.5 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. Dirtyphones.org needs all CSS files to be minified and compressed as it can save up to 296.8 kB or 91% of the original size.

Requests Breakdown

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

Requests Now

70

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dirtyphones. 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 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.dirtyphones.org

www.dirtyphones.org

1777 ms

foundation.css

foundation.css

1741 ms

custom_foundation.css

custom_foundation.css

656 ms

layout.css

layout.css

895 ms

nav_slider.css

nav_slider.css

1355 ms

modernizr.js

modernizr.js

679 ms

twitter_widget.js

twitter_widget.js

1261 ms

fb_all.js

fb_all.js

1958 ms

platform.js

platform.js

51 ms

conversion.js

conversion.js

35 ms

jquerysctipttop.css

jquerysctipttop.css

896 ms

jquery.js

jquery.js

1159 ms

foundation.min.js

foundation.min.js

1666 ms

foundation.topbar.js

foundation.topbar.js

875 ms

jquery.min.js

jquery.min.js

1186 ms

social_function.js

social_function.js

1093 ms

jquery.inview.js

jquery.inview.js

1311 ms

320.css

320.css

1064 ms

768.css

768.css

1090 ms

1024.css

1024.css

1118 ms

1280.css

1280.css

1244 ms

1440.css

1440.css

1282 ms

1920.css

1920.css

1283 ms

fbds.js

fbds.js

304 ms

74 ms

sony_logo_mobile.png

sony_logo_mobile.png

222 ms

results_heading.png

results_heading.png

229 ms

result_germs.png

result_germs.png

447 ms

result_footer.png

result_footer.png

224 ms

facebook_icon.png

facebook_icon.png

222 ms

twitter_icon.png

twitter_icon.png

225 ms

googl_plus_icon.png

googl_plus_icon.png

439 ms

public_low_1440.jpg

public_low_1440.jpg

1960 ms

heres_dirty_secret.png

heres_dirty_secret.png

1092 ms

heres_dirty_secret_mobile.png

heres_dirty_secret_mobile.png

660 ms

heres_dirty_secret_arrow.png

heres_dirty_secret_arrow.png

443 ms

heres_dirty_secret_mobile_arrow.png

heres_dirty_secret_mobile_arrow.png

659 ms

multiple_img_1440.jpg

multiple_img_1440.jpg

1314 ms

because_your_touch_phone.png

because_your_touch_phone.png

886 ms

hand_1440.jpg

hand_1440.jpg

1312 ms

but_your_phones.png

but_your_phones.png

1533 ms

tap_running_1440.jpg

tap_running_1440.jpg

1327 ms

one_of_the_easiest.png

one_of_the_easiest.png

1310 ms

blue_arrow.png

blue_arrow.png

1528 ms

mobile_wash_1440.jpg

mobile_wash_1440.jpg

2181 ms

discover_the_m4aqua.png

discover_the_m4aqua.png

1535 ms

washing_instructions.png

washing_instructions.png

1547 ms

washing_instructions_content.png

washing_instructions_content.png

1750 ms

xperia_m4_aqua_dual.png

xperia_m4_aqua_dual.png

1756 ms

xperia_z3_plus.png

xperia_z3_plus.png

1754 ms

xperia_z3.png

xperia_z3.png

1767 ms

xperia_z3_compact.png

xperia_z3_compact.png

1970 ms

xperia_z1.png

xperia_z1.png

1973 ms

xperia_z1_compact.png

xperia_z1_compact.png

1974 ms

xperia_z_ultra.png

xperia_z_ultra.png

1988 ms

xperia_z2.png

xperia_z2.png

2175 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

42 ms

RockwellStd.woff

RockwellStd.woff

2150 ms

RockwellStd-Italic.woff

RockwellStd-Italic.woff

2156 ms

80 ms

analytics.js

analytics.js

85 ms

hub.495aa91f8927e5f490215e98e950746c.html

hub.495aa91f8927e5f490215e98e950746c.html

71 ms

postmessageRelay

postmessageRelay

73 ms

collect

collect

20 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

27 ms

rpc:shindig_random.js

rpc:shindig_random.js

31 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

9 ms

auth

auth

87 ms

xd_arbiter.php

xd_arbiter.php

8 ms

22 ms

68 ms

xd_arbiter.php

xd_arbiter.php

9 ms

2637085964-postmessage.js

2637085964-postmessage.js

6 ms

21 ms

Accessibility Review

dirtyphones.org accessibility score

63

Accessibility Issues

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.

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

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

dirtyphones.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

dirtyphones.org SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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 doesn't use legible font sizes

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

dirtyphones.org

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