4.5 sec in total
186 ms
2.9 sec
1.4 sec
Visit round.me now to see the best up-to-date Round content for Belarus and also check out these interesting facts you probably never knew about round.me
Roundme - create, upload, license and embed 360° degree VR and gigapixel panoramic pictures and virtual tours online.
Visit round.meWe analyzed Round.me page load time and found that the first response time was 186 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
round.me performance score
name
value
score
weighting
Value6.0 s
3/100
10%
Value18.2 s
0/100
25%
Value10.5 s
7/100
10%
Value1,240 ms
19/100
30%
Value0.088
93/100
15%
Value18.2 s
3/100
10%
186 ms
490 ms
84 ms
123 ms
241 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 7% of them (7 requests) were addressed to the original Round.me, 51% (53 requests) were made to Static.round.me and 13% (13 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (923 ms) relates to the external source Static.round.me.
Page size can be reduced by 1.8 MB (36%)
4.9 MB
3.1 MB
In fact, the total size of Round.me main page is 4.9 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 2.4 MB which makes up the majority of the site volume.
Potential reduce by 44.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 44.5 kB or 81% of the original size.
Potential reduce by 32.5 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. Round images are well optimized though.
Potential reduce by 1.4 MB
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 1.4 MB or 68% of the original size.
Potential reduce by 277.4 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. Round.me needs all CSS files to be minified and compressed as it can save up to 277.4 kB or 85% of the original size.
Number of requests can be reduced by 23 (26%)
88
65
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Round. 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 as a result speed up the page load time.
round.me
186 ms
round.me
490 ms
all.min.css
84 ms
vendor-003af8e4aa3ab7460eca.js
123 ms
app-003af8e4aa3ab7460eca.js
241 ms
js
107 ms
analytics.js
145 ms
isauthorize
141 ms
betaeasy2.js
45 ms
2_silver.png
21 ms
contributionForm.html.js
10 ms
html2canvas.js
20 ms
proxima-nova-regular.otf
12 ms
fb-big.svg
128 ms
main
523 ms
mainmap
300 ms
business
337 ms
main
305 ms
twitt-big.svg
52 ms
gogl-big.svg
52 ms
logo-white.svg
67 ms
lock-icon.svg
66 ms
finish-bg.jpg
68 ms
video-big.jpg
72 ms
about-rm.jpg
105 ms
dot.png
71 ms
r-icon.png
73 ms
appstore-white.svg
102 ms
google-play.svg
79 ms
scrolldown.svg
106 ms
proxima-nova-semibold.otf
102 ms
proxima-nova-thin.otf
98 ms
proxima-nova-light.otf
102 ms
collect
74 ms
create-spaces-bg.jpg
66 ms
left-arrow.png
67 ms
right-arrow.png
67 ms
map-overlay.png
70 ms
for-professionals-bg.jpg
853 ms
for-professionals-camera.png
70 ms
iphone-app.jpg
86 ms
iphone-app-devices.png
84 ms
collect
61 ms
all.js
542 ms
common.js
62 ms
map.js
120 ms
util.js
100 ms
marker.js
117 ms
overlay.js
91 ms
2058.jpg
499 ms
9a35697fe30d7181894d9746b977e04413295af3.jpg
93 ms
video-button.svg
51 ms
StaticMapService.GetMapImage
291 ms
8003588a68c8366c9a05bb04dc16360ea2df98bd.png
62 ms
d78835157379e4d1124468b03a5847f007c48182.jpg
73 ms
30c9623f0a9f4791d1bf9a814e740369fa721ed7.jpg
66 ms
1350.jpg
49 ms
2117.jpg
650 ms
269.jpg
73 ms
1362.jpg
74 ms
892.jpg
74 ms
1526.jpg
614 ms
onion.js
98 ms
transparent.png
238 ms
kh
242 ms
kh
241 ms
controls.js
111 ms
1362.png
546 ms
1978.png
119 ms
2058.png
584 ms
3727.png
724 ms
1561.png
400 ms
1547.png
409 ms
1350.png
417 ms
34841.png
433 ms
2093.png
436 ms
892.png
446 ms
kh
248 ms
kh
272 ms
kh
250 ms
kh
274 ms
kh
271 ms
kh
272 ms
kh
270 ms
ViewportInfoService.GetViewportInfo
168 ms
stats.js
111 ms
StaticMapService.GetMapImage
225 ms
2058.jpg
923 ms
pin-default.png
390 ms
css
236 ms
transparent.png
150 ms
google4.png
198 ms
mapcnt6.png
159 ms
sv5.png
196 ms
google_white5.png
148 ms
AuthenticationService.Authenticate
47 ms
98 ms
xd_arbiter.php
445 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
73 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
97 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
134 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
135 ms
xd_arbiter.php
139 ms
round.me accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<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
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.
round.me 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
Browser errors were logged to the console
Page has valid source maps
round.me SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Round.me 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 Round.me 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.
round.me
Open Graph data is detected on the main page of Round. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: