1.7 sec in total
121 ms
1.2 sec
339 ms
Click here to check amazing Planet Earth Singles content for United States. Otherwise, check out these important facts you probably never knew about planetearthsingles.com
Planet Earth Singles: Dating for Green Singles, Vegan Singles, Vegetarian Singles. Meet your eco-conscious match here. Best dating site.
Visit planetearthsingles.comWe analyzed Planetearthsingles.com page load time and found that the first response time was 121 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
planetearthsingles.com performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value7.5 s
4/100
25%
Value5.4 s
57/100
10%
Value450 ms
63/100
30%
Value0.13
82/100
15%
Value9.9 s
27/100
10%
121 ms
291 ms
39 ms
41 ms
41 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 89% of them (63 requests) were addressed to the original Planetearthsingles.com, 7% (5 requests) were made to Google-analytics.com and 1% (1 request) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (513 ms) belongs to the original domain Planetearthsingles.com.
Page size can be reduced by 390.1 kB (22%)
1.8 MB
1.4 MB
In fact, the total size of Planetearthsingles.com main page is 1.8 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. 45% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 105.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 15.1 kB, which is 11% 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 105.9 kB or 79% of the original size.
Potential reduce by 146.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. Obviously, Planet Earth Singles needs image optimization as it can save up to 146.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 107.4 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 107.4 kB or 53% of the original size.
Potential reduce by 30.8 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. Planetearthsingles.com needs all CSS files to be minified and compressed as it can save up to 30.8 kB or 83% of the original size.
Number of requests can be reduced by 18 (27%)
67
49
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Planet Earth Singles. 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 4 to 1 for CSS and as a result speed up the page load time.
planetearthsingles.com
121 ms
www.planetearthsingles.com
291 ms
styles_individual.css
39 ms
styles_common.css
41 ms
carrousel.css
41 ms
jquery-1.7.2.min.js
64 ms
jquery.jcarousel.0.2.8.min.js
61 ms
new_general_scripts.js
61 ms
jquery.validate.min.js
62 ms
jquery.tools.min.js
63 ms
jquery.totemticker.min.js
62 ms
jquery.cycle.lite.js
77 ms
main_top1.jpg
137 ms
urchin.js
23 ms
conversion.js
18 ms
bg.jpg
230 ms
main_top2.jpg
88 ms
bg_button_login1.jpg
83 ms
bg_button_join2.jpg
84 ms
big_image_home1.jpg
97 ms
big_image_home2.jpg
115 ms
big_image_home3.jpg
96 ms
big_image_home4.jpg
113 ms
big_image_home5.jpg
131 ms
bg_white_transparent.png
114 ms
bg_button_qs1.jpg
113 ms
photo_resized.php
172 ms
photo_resized.php
171 ms
photo_resized.php
172 ms
photo_resized.php
174 ms
photo_resized.php
192 ms
photo_resized.php
513 ms
photo_resized.php
234 ms
photo_resized.php
237 ms
photo_resized.php
232 ms
photo_resized.php
272 ms
photo_resized.php
288 ms
photo_resized.php
293 ms
photo_resized.php
288 ms
photo_resized.php
289 ms
photo_resized.php
330 ms
bg_lower_bar.jpg
307 ms
logo_cdn.png
308 ms
couple_bottom.jpg
345 ms
bulletpurple.gif
313 ms
couple2_bottom.jpg
324 ms
logo_bottom.jpg
325 ms
hands_bottom.jpg
359 ms
__utm.gif
57 ms
ga.js
59 ms
69 ms
load_orientation.php
310 ms
load_orientation.php
299 ms
castlen-webfont.woff
273 ms
couple3_bottom.jpg
289 ms
logo_b_2.jpg
290 ms
slider_button_left.png
297 ms
inpage_linkid.js
18 ms
slider_button_right.png
298 ms
39 ms
__utm.gif
13 ms
mobile-index.css
22 ms
image_thumb.php
110 ms
image_thumb.php
111 ms
image_thumb.php
111 ms
image_thumb.php
108 ms
image_thumb.php
237 ms
image_thumb.php
129 ms
image_thumb.php
185 ms
image_thumb.php
178 ms
image_thumb.php
198 ms
planetearthsingles.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
planetearthsingles.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
planetearthsingles.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Planetearthsingles.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 Planetearthsingles.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.
planetearthsingles.com
Open Graph description is not detected on the main page of Planet Earth Singles. 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: