3.7 sec in total
478 ms
2.6 sec
685 ms
Click here to check amazing Greybe content. Otherwise, check out these important facts you probably never knew about greybe.com
Thomas Henry Greybe is a Digital Creative Director with a focus on Design and over 10 years experience in the industry.
Visit greybe.comWe analyzed Greybe.com page load time and found that the first response time was 478 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
greybe.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value20.5 s
0/100
25%
Value10.0 s
9/100
10%
Value380 ms
70/100
30%
Value0.011
100/100
15%
Value13.9 s
10/100
10%
478 ms
68 ms
298 ms
186 ms
282 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 94% of them (94 requests) were addressed to the original Greybe.com, 4% (4 requests) were made to Use.typekit.net and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Greybe.com.
Page size can be reduced by 242.4 kB (4%)
5.8 MB
5.6 MB
In fact, the total size of Greybe.com main page is 5.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. 55% of websites need less resources to load. Images take 5.4 MB which makes up the majority of the site volume.
Potential reduce by 36.1 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 36.1 kB or 74% of the original size.
Potential reduce by 0 B
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. Greybe images are well optimized though.
Potential reduce by 206.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 206.3 kB or 63% of the original size.
Potential reduce by 0 B
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.
We found no issues to fix!
96
96
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greybe. According to our analytics all requests are already optimized.
greybe.com
478 ms
js
68 ms
ckf7ljy.css
298 ms
index.d73f7ad5.css
186 ms
index.e9a2d1b4.js
282 ms
index.b5e7c14d.js
386 ms
p.css
29 ms
BS_1_1.07db00d9.png
277 ms
VF_1_1.8ace8a8c.png
178 ms
SKY_1_1.34564b81.png
269 ms
FYNS_1_1.abfc3bdd.png
372 ms
HFTC_1_1.47ece473.png
218 ms
EBAY_1_1.44dfe6b0.png
363 ms
MOTM_1_1.5b339b7a.png
315 ms
OLIO_1_1.c0622504.png
315 ms
SUPER_1_1.03cc3c6d.png
447 ms
JLR_1_1.png
818 ms
BS_1_1.png
418 ms
EBAY_1_1.png
497 ms
OLIO_1_1.png
727 ms
VF_1_1.png
567 ms
FYNS_1_1.png
597 ms
MOTM_1_1.png
628 ms
SKY_1_1.png
588 ms
HFTC_1_1.png
936 ms
SUPER_1_1.png
768 ms
MOZ_1_1.png
689 ms
MEGAN_1_1.png
806 ms
ALIGN_1_1.png
794 ms
PIXMA_1_2.png
827 ms
JLR_1_1.0a660f9e.png
856 ms
JLR_1_2.e6aee776.png
892 ms
JLR_1_3.562e177d.png
895 ms
JLR_1_4.17f86860.png
913 ms
JLR_1_5.58b34466.png
917 ms
BS_1_1.3bfc0453.png
944 ms
BS_1_2.5e46354f.png
988 ms
BS_1_3.6c971cba.png
983 ms
BS_1_4.bc6de463.png
1006 ms
EBAY_1_1.ddb4263e.png
1005 ms
EBAY_1_2.be56696d.png
1029 ms
d
26 ms
d
9 ms
d
27 ms
EBAY_1_3.b5037796.png
924 ms
EBAY_1_4.5aa5d993.png
905 ms
EBAY_1_5.47a89863.png
866 ms
EBAY_1_6.78a230ec.png
880 ms
OLIO_1_1.01dd458e.png
837 ms
OLIO_1_2.46f5085f.png
850 ms
OLIO_1_3.e9da387f.png
821 ms
OLIO_1_4.f4aff855.png
866 ms
OLIO_1_5.47f9b6eb.png
819 ms
VF_1_1.b4f81d62.png
817 ms
VF_1_2.e4288865.png
783 ms
VF_1_3.37e1295e.png
769 ms
VF_1_4.d205fa53.png
733 ms
VF_1_5.847fc940.png
710 ms
FYNS_1_1.2b114daf.png
685 ms
FYNS_1_2.03652fc7.png
684 ms
FYNS_1_3.f1ad19c3.png
660 ms
FYNS_1_4.cc3de746.png
618 ms
FYNS_1_5.ddb549d8.png
592 ms
FYNS_1_6.fbe83a19.png
598 ms
MOTM_1_1.77d09212.png
570 ms
MOTM_1_2.a29104ee.png
566 ms
MOTM_1_3.412a41d4.png
560 ms
MOTM_1_4.8e57cd32.png
571 ms
SKY_1_1.80302c76.png
552 ms
SKY_1_2.17c93686.png
563 ms
SKY_1_3.dd1a6e07.png
559 ms
SKY_1_4.085d5dc9.png
547 ms
SKY_1_5.b93b2e03.png
549 ms
HFTC_1_1.aa6a61cf.png
555 ms
HFTC_1_2.a5c3d5d1.png
552 ms
HFTC_1_3.b8445143.png
564 ms
HFTC_1_4.2c0ce229.png
557 ms
HFTC_1_5.592a5024.png
544 ms
SUPER_1_1.453551da.png
548 ms
SUPER_1_2.71902158.png
555 ms
SUPER_1_3.9e87650b.png
551 ms
SUPER_1_4.c30f5dba.png
561 ms
SUPER_1_5.e0238fc0.png
556 ms
MOZ_1_1.176ebda2.png
550 ms
MOZ_1_2.9affe4ae.png
541 ms
MOZ_1_3.8d079c98.png
553 ms
MOZ_1_4.e469a418.png
542 ms
MOZ_1_5.2fdabbfb.png
560 ms
MEGAN_1_1.f8c6dcb9.png
554 ms
MEGAN_1_2.95355143.png
551 ms
MEGAN_1_3.8d0b4ecf.png
537 ms
MEGAN_1_4.49bc6673.png
550 ms
ALIGN_1_1.65aa1bd6.png
544 ms
ALIGN_1_2.bb6f70d3.png
557 ms
ALIGN_1_3.6000b742.png
551 ms
ALIGN_1_4.115e2fcc.png
549 ms
ALIGN_1_5.33f6cd9f.png
539 ms
PIXMA_1_1.ba34807c.png
554 ms
PIXMA_1_2.61efb236.png
546 ms
THG_pic.068f3a51.png
552 ms
greybe.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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
greybe.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
greybe.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greybe.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 Greybe.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.
greybe.com
Open Graph description is not detected on the main page of Greybe. 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: