5.3 sec in total
607 ms
4.6 sec
125 ms
Visit ref.so now to see the best up-to-date Ref content for China and also check out these interesting facts you probably never knew about ref.so
This domain may be for sale!
Visit ref.soWe analyzed Ref.so page load time and found that the first response time was 607 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
ref.so performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value3.9 s
53/100
25%
Value3.5 s
89/100
10%
Value190 ms
91/100
30%
Value0.029
100/100
15%
Value4.0 s
88/100
10%
607 ms
408 ms
138 ms
72 ms
227 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 96% of them (54 requests) were addressed to the original Ref.so, 4% (2 requests) were made to Count44.51yes.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Count44.51yes.com.
Page size can be reduced by 563.0 kB (78%)
718.3 kB
155.3 kB
In fact, the total size of Ref.so main page is 718.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 402.4 kB which makes up the majority of the site volume.
Potential reduce by 30.2 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 5.3 kB, which is 14% 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 30.2 kB or 82% of the original size.
Potential reduce by 303.1 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, Ref needs image optimization as it can save up to 303.1 kB or 75% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 181.8 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.8 kB or 82% of the original size.
Potential reduce by 48.0 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. Ref.so needs all CSS files to be minified and compressed as it can save up to 48.0 kB or 82% of the original size.
Number of requests can be reduced by 22 (40%)
55
33
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ref. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
www.ref.so
607 ms
main.css
408 ms
blank.gif
138 ms
jcllib.css
72 ms
jcl_ui.js
227 ms
en_us.js
141 ms
jcllib.js
680 ms
click.aspx
2314 ms
tail-top.gif
72 ms
lang_bg.gif
70 ms
lang_list.png
204 ms
logo.png
275 ms
newurl.png
138 ms
button.png
204 ms
left-top-corner1.png
134 ms
right-top-corner1.png
201 ms
border-top1.gif
203 ms
border-left1.gif
267 ms
border-right1.gif
267 ms
extra-border-bot1.gif
269 ms
extra-left-corner1.jpg
271 ms
extra-right-corner1.jpg
335 ms
link1-right.png
336 ms
link1-left.png
339 ms
link1-tail.png
337 ms
left-bot-corner1.png
339 ms
right-bot-corner1.png
402 ms
border-bot1.gif
403 ms
left-top-corner4.png
405 ms
right-top-corner4.png
404 ms
border-top4.gif
406 ms
border-left4.gif
432 ms
border-right4.gif
469 ms
extra-border-bot4.gif
470 ms
extra-left-corner4.jpg
472 ms
extra-right-corner4.jpg
473 ms
left-bot-corner4.png
475 ms
right-bot-corner4.png
500 ms
border-bot4.gif
535 ms
left-top-corner3.png
537 ms
right-top-corner3.png
540 ms
border-top3.gif
542 ms
border-left3.gif
542 ms
border-right3.gif
506 ms
extra-border-bot3.gif
541 ms
extra-left-corner3.jpg
476 ms
extra-right-corner3.jpg
478 ms
circle_red.png
550 ms
arrow_left.png
483 ms
circle_green.png
505 ms
circle_blue.png
540 ms
circle_yellow.png
477 ms
left-bot-corner3.png
414 ms
right-bot-corner3.png
481 ms
border-bot3.gif
482 ms
count1.gif
999 ms
ref.so 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.
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
<frame> or <iframe> elements do not have a title
ref.so best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
ref.so SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document doesn't use 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 Ref.so 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 Ref.so 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.
ref.so
Open Graph description is not detected on the main page of Ref. 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: