1.9 sec in total
41 ms
1.3 sec
497 ms
Visit yardmap.org now to see the best up-to-date Yardmap content for Indonesia and also check out these interesting facts you probably never knew about yardmap.org
Visit yardmap.orgWe analyzed Yardmap.org page load time and found that the first response time was 41 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.
yardmap.org performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value3.6 s
61/100
25%
Value3.6 s
86/100
10%
Value360 ms
72/100
30%
Value0
100/100
15%
Value3.8 s
89/100
10%
41 ms
42 ms
315 ms
35 ms
58 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Yardmap.org, 73% (47 requests) were made to Content.yardmap.org and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (650 ms) relates to the external source Content.yardmap.org.
Page size can be reduced by 474.4 kB (14%)
3.5 MB
3.0 MB
In fact, the total size of Yardmap.org main page is 3.5 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 2.8 MB which makes up the majority of the site volume.
Potential reduce by 147.3 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 147.3 kB or 56% of the original size.
Potential reduce by 65.3 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. Yardmap images are well optimized though.
Potential reduce by 181.3 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 181.3 kB or 64% of the original size.
Potential reduce by 80.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. Yardmap.org needs all CSS files to be minified and compressed as it can save up to 80.5 kB or 83% of the original size.
Number of requests can be reduced by 16 (29%)
56
40
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yardmap. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
yardmap.org
41 ms
www.yardmap.org
42 ms
content.yardmap.org
315 ms
css
35 ms
base2015.css
58 ms
home2015.css
77 ms
modernizr-2.7-wflexbox.js
80 ms
picturefill.min.js
53 ms
handlebars-v1.3.0.js
92 ms
d3.v3.min.js
11 ms
topojson.v1.min.js
10 ms
jquery.min.js
115 ms
jquery.timeago.js
46 ms
jquery.waypoints.min.js
83 ms
home2015.js
126 ms
mailchimp-ajax.js
111 ms
ga.js
113 ms
95627.js
113 ms
world-50m.json
142 ms
activity
78 ms
statistics
75 ms
logos.png
133 ms
menu.svg
40 ms
user.svg
70 ms
account.jpg
70 ms
tree1-animate.png
220 ms
tree2-animate.png
293 ms
orange-loader.gif
134 ms
arrow-down.svg
133 ms
bg.jpg
209 ms
house1.png
352 ms
house2.png
358 ms
house3.png
332 ms
house4.png
323 ms
house5.png
340 ms
replay.svg
328 ms
map.svg
364 ms
leaf.svg
367 ms
earth.svg
372 ms
anatomy1.png
524 ms
anatomy2.png
425 ms
anatomy3.png
433 ms
obj-tree.png
415 ms
obj-shrub.png
416 ms
obj-feeder.png
409 ms
learn.jpg
494 ms
share.jpg
507 ms
group.jpg
510 ms
native-gardeners.jpg
500 ms
birders.jpg
501 ms
educators.jpg
562 ms
wildlife-enthusiasts.jpg
569 ms
stars.jpg
650 ms
give-me-a-home.jpg
642 ms
camera.svg
546 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
30 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
67 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
68 ms
4cKlrioa77J2iqTqBgkRWg.ttf
69 ms
fec-img.png
603 ms
__utm.gif
47 ms
collect
141 ms
map-icons.png
503 ms
__ptq.gif
15 ms
yardmap.org accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
yardmap.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
yardmap.org SEO score
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
ID
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yardmap.org can be misinterpreted by Google and other search engines. Our service has detected that is used on the page, and it does not match the claimed English language. Our system also found out that Yardmap.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.
yardmap.org
Open Graph data is detected on the main page of Yardmap. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: