5.1 sec in total
845 ms
2.5 sec
1.8 sec
Visit relic.com now to see the best up-to-date Relic content for China and also check out these interesting facts you probably never knew about relic.com
Visit relic.comWe analyzed Relic.com page load time and found that the first response time was 845 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
relic.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value5.5 s
19/100
25%
Value21.8 s
0/100
10%
Value7,280 ms
0/100
30%
Value0.689
7/100
15%
Value30.0 s
0/100
10%
845 ms
62 ms
70 ms
63 ms
72 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Relic.com, 80% (70 requests) were made to Assets.relic.com and 9% (8 requests) were made to . The less responsive or slowest element that took the longest time to load (845 ms) belongs to the original domain Relic.com.
Page size can be reduced by 967.6 kB (10%)
9.8 MB
8.8 MB
In fact, the total size of Relic.com main page is 9.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. 85% 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 9.1 MB which makes up the majority of the site volume.
Potential reduce by 115.6 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 115.6 kB or 84% of the original size.
Potential reduce by 469.2 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. Relic images are well optimized though.
Potential reduce by 166.2 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 166.2 kB or 68% of the original size.
Potential reduce by 216.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. Relic.com needs all CSS files to be minified and compressed as it can save up to 216.5 kB or 84% of the original size.
Number of requests can be reduced by 13 (17%)
77
64
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Relic. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.relic.com
845 ms
css_B6dMI0p-TaKQiKvIWPoqM6iNo2FimeE1Yf1XnH_n77I.css
62 ms
css_uRObVJ6y9-OVaJzgRxdE0ZUTvdkVTx1KJn0jmhRvPu0.css
70 ms
css_TUT2q27QvGnvfwnTu3OEUbDJjh5lwz6jLhzsf45jS0I.css
63 ms
css_c_VekbtM9DG4HTod-SC7I3_Oalmf0wNkr2spy-d2qCs.css
72 ms
logo.png
54 ms
js_REsLPu7rmWMjWdJcbmAAi4_CGneW_u1kgEQ0gfYfPC4.js
42 ms
gnv6rcw.js
173 ms
js_MpKfe1sTh5JIVGCZ17DsAuT1rqAC38MLLlkjqjQ1X_k.js
136 ms
js_yAicZujtqUhpCyuBiQyVA1uGwMX8V0A0ym_4Jb35kBQ.js
134 ms
js_n_NBmSxeKKIJQBiI6LNTLXjOsFzRb5AGK5iWRv9uwUU.js
134 ms
js_juDMXOAivyNZSIlaQ9Z7T5qWsYCR2iU_qujuOXb15As.js
138 ms
studio1.jpg
138 ms
studio3.jpg
152 ms
studio9.jpg
141 ms
kitchen.jpg
149 ms
RELIC_OFFICE_204.jpg
139 ms
Sumo_0.jpg
148 ms
warhammer.jpg
223 ms
RELIC_043015_105.jpg
155 ms
relic_0.jpg
154 ms
relic_23.jpg
243 ms
secondary_logo.png
221 ms
logo_s.png
100 ms
coh_image_1.jpg
104 ms
coh_image_2.png
106 ms
coh_image_3.png
110 ms
dow_image_1.jpg
150 ms
dow_image_2_0.png
113 ms
dow_image_3.png
119 ms
sm_image_1.jpg
145 ms
sm_image_2_0.png
160 ms
sm_image_3.png
131 ms
Leadership_Justin_0.jpg
151 ms
Leadership_Greg.jpg
150 ms
Leadership_AlexP_0.jpg
164 ms
Leadership_Curtis_0.jpg
281 ms
Leadership_Jillian.jpg
192 ms
Outdoors.jpg
183 ms
Stanley.jpg
195 ms
Dining.jpg
178 ms
Yaletown.jpg
221 ms
Canucks_0.jpg
265 ms
Whistler.jpg
221 ms
Chinese.jpg
227 ms
1.jpg
225 ms
fi-1997.png
231 ms
2.jpg
250 ms
fi-1999_0.png
256 ms
3.jpg
240 ms
fi-2003.png
244 ms
4.jpg
252 ms
fi-2004.png
267 ms
5.jpg
478 ms
fi-2006.png
256 ms
6_0.jpg
263 ms
d
248 ms
fi-2009.png
409 ms
7.jpg
409 ms
fi-2010.png
201 ms
8.jpg
405 ms
fi-2011.png
401 ms
9.jpg
401 ms
fi-2013.png
524 ms
GGJ_BLOG_1900_0_0.jpg
395 ms
VFS_1900.jpg
392 ms
manhole_procedural_1900.jpg
381 ms
EXTRALIFETEAM1900.jpg
367 ms
analytics.js
163 ms
SUFZQVXBSMFBIUAhBOxeIwYI0AGTegzoQA5D5CXDK4bXDG8Y3jIcYrgMAL0RQrg=
21 ms
SUFZQVXBSMFBIUAhBOxeIwYI0AGTegzoQA5D5CXDK4bXDG8Y3jIcYrgMAL0RQrg=
21 ms
qS2sGeb2dSe7AHe5qqrobaudKO77N82f3WRzRbHFecu76R88MkXa14PvIFCsgA=
19 ms
dZHNFscV5y7vpHzwyRdrXg+8gUKyAA==
19 ms
h7vwq58kP4rf6ktrBnm9nUnuwB3uaqq6G2rnSju+zfNn91kc0WxxXnLu+kfPDJF2teD7yBQrIA
18 ms
qS2sGeb2dSe7AHe5qqrobaudKO77N82f3WRzRbHFecu76R88MkXa14PvIFCsgA=
17 ms
8MPIkzTmwAA
16 ms
B9+ADKu06UA
15 ms
linkid.js
35 ms
collect
51 ms
p.gif
632 ms
video_placeholder.jpg
547 ms
iframe_api
370 ms
m_tip.png
57 ms
map.png
40 ms
foundation-icons_ed4a4c41920dc6fe7ebb97c0f6d962d6.svg
148 ms
foundation-icons_ed4a4c41920dc6fe7ebb97c0f6d962d6.woff
50 ms
www-widgetapi.js
109 ms
relic.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.
relic.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
relic.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Relic.com 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 Relic.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.
relic.com
Open Graph description is not detected on the main page of Relic. 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: