2 sec in total
198 ms
1.2 sec
578 ms
Welcome to custom.live homepage info - get ready to check Custom best content right away, or after learning these important things about custom.live
Custom Live 是一間專注提供現場印製服務的專家。我們為品牌及市場營銷公司提供一站式的現場印製高品質產品服務。不但令你的客戶能得到高品質的定制產品,香港首創現場客制化方案 個個都用Photobooth|唔通個個Photobooth 有效咩?
Visit custom.liveWe analyzed Custom.live page load time and found that the first response time was 198 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.
custom.live performance score
name
value
score
weighting
Value1.6 s
94/100
10%
Value9.7 s
0/100
25%
Value9.5 s
11/100
10%
Value870 ms
33/100
30%
Value0.017
100/100
15%
Value10.9 s
21/100
10%
198 ms
315 ms
233 ms
68 ms
150 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 92% of them (48 requests) were addressed to the original Custom.live, 4% (2 requests) were made to Connect.facebook.net and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (526 ms) belongs to the original domain Custom.live.
Page size can be reduced by 253.2 kB (7%)
3.6 MB
3.4 MB
In fact, the total size of Custom.live main page is 3.6 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. Only a small number of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 73.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 73.5 kB or 79% of the original size.
Potential reduce by 167.0 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. Custom images are well optimized though.
Potential reduce by 17 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 12.7 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. Custom.live needs all CSS files to be minified and compressed as it can save up to 12.7 kB or 13% of the original size.
Number of requests can be reduced by 21 (43%)
49
28
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Custom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
custom.live
198 ms
main.5880ee1e04464723f0d2fb076f0adfc1.css
315 ms
dynamic.522ca3eb3182f0587a082a9a14102392.css
233 ms
js
68 ms
0-4a20e5f756891cf58825cbf419441f6b-nitro-mini-d41d8cd98f00b204-cefca2272753c05bb9322eee792e6631.css
150 ms
slick.css
130 ms
slick-theme.css
165 ms
email-decode.min.js
41 ms
lazysizes.min.js
169 ms
jquery.min.js
259 ms
jquery-migrate.min.js
261 ms
bootstrap.min.js
277 ms
mightyslider.min.js
376 ms
tweenlite.min.js
517 ms
app.js
376 ms
libs.min.js
374 ms
common.js
517 ms
0-4a20e5f756891cf58825cbf419441f6b-nitro-mini-d41d8cd98f00b204-3e7a1db701cfbe669f07e04b6c97b5f7.js
519 ms
0-4a20e5f756891cf58825cbf419441f6b-nitro-mini-d41d8cd98f00b204-d558dbd44c2c02f9ecc3d80e102ca832.js
526 ms
slick.min.js
522 ms
Logo_web-02.png
75 ms
gb.png
158 ms
zh-HK.png
161 ms
hand.png
162 ms
monitor.png
161 ms
ezgif.com-video-to-gif.gif
167 ms
bottle.png
168 ms
totebag.png
167 ms
adidas_counter.png
169 ms
adidas_photo.png
170 ms
bg_shop.png
174 ms
pixel.gif
172 ms
tee-subli.png
171 ms
tote.png
171 ms
tapestries.png
178 ms
mug.png
172 ms
case.png
174 ms
pillow.png
175 ms
tee-dtg.png
177 ms
hat.png
179 ms
hoodie.png
179 ms
light.png
162 ms
all.js
137 ms
dynamic.522ca3eb3182f0587a082a9a14102392.css
280 ms
fontawesome-webfont.woff
274 ms
product_background.jpg
36 ms
all.js
24 ms
icons.svg
61 ms
ajax-loader.gif
62 ms
slick.woff
116 ms
mosaic_s.png
38 ms
css
121 ms
custom.live 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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 valid value for its [lang] attribute.
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.
custom.live 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
custom.live 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
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
Tap targets are not sized appropriately
EN
CO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Custom.live can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Corsican language. Our system also found out that Custom.live 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.
custom.live
Open Graph description is not detected on the main page of Custom. 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: