3.6 sec in total
872 ms
2.1 sec
612 ms
Click here to check amazing Full Line content. Otherwise, check out these important facts you probably never knew about fullline.ca
Welcome to Full Line Specialties, where promoting your business is our business. Born in 1996 from an expertise in building brands, we offer unique, quality promotional products, excellent service and...
Visit fullline.caWe analyzed Fullline.ca page load time and found that the first response time was 872 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
fullline.ca performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value7.3 s
5/100
25%
Value11.8 s
4/100
10%
Value610 ms
49/100
30%
Value0.253
49/100
15%
Value30.3 s
0/100
10%
872 ms
150 ms
379 ms
135 ms
32 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 39% of them (26 requests) were addressed to the original Fullline.ca, 40% (27 requests) were made to Tscstatic.fullline.ca and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (872 ms) belongs to the original domain Fullline.ca.
Page size can be reduced by 301.7 kB (5%)
5.5 MB
5.2 MB
In fact, the total size of Fullline.ca main page is 5.5 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. 60% of websites need less resources to load. Images take 5.4 MB which makes up the majority of the site volume.
Potential reduce by 115.0 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 33.9 kB, which is 25% 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 115.0 kB or 86% of the original size.
Potential reduce by 186.7 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. Full Line images are well optimized though.
Potential reduce by 12 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.
Number of requests can be reduced by 16 (28%)
57
41
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Full Line. 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 8 to 1 for CSS and as a result speed up the page load time.
fullline.ca
872 ms
www.fullline.ca
150 ms
www.fullline.ca
379 ms
js
135 ms
css
32 ms
css
49 ms
css
58 ms
f926cc00fb.js
75 ms
Core
63 ms
airy
93 ms
airy-product-bundle
68 ms
GetCss
73 ms
airy-home-bundle
68 ms
core
310 ms
airy
76 ms
airy-product-grid
112 ms
airy-home-bundle
115 ms
api.js
33 ms
core.js
38 ms
hotjar-1646832.js
132 ms
logo_VDPVTV3WK0.png
334 ms
306904607
304 ms
SAMSINGH-portrait-0WXO.png
47 ms
JohnGirling-portrait-K9N5.png
168 ms
TonyShaer-portrait-1FDU.png
165 ms
CorinnaBuc-head-shot-M57CCH5.jpg
75 ms
JesseDearm-head-shot-5YOL2MV.jpg
83 ms
IrynaChernii-portrait-8E68.png
168 ms
DavidMcAlary-portrait-L7QD.png
186 ms
DeanLongstaff-portrait-XPRV.png
188 ms
MarkSlade-portrait-5VSH.png
189 ms
KrisLittle-portrait-QL9O.png
288 ms
RafiAbdulahad-portrait-6KUR.png
306 ms
BillMacPhee-portrait-RIGX.png
290 ms
t1Brandthe_1_1Y3U4U7AUIFBT6.jpg
443 ms
t1TheStude_1_611LOSURIVCOJH.jpg
449 ms
GetOutdoor_p1_l5_1_ANGPD2O25PMCAD.jpg
388 ms
Golf_p1_l6_1_MUG04N7A7H8LS7.jpg
394 ms
Distinctiv_p1_l7_1_RCIHZ4XLOIQZ2K.jpg
406 ms
SelfCare_p1_l8_1_IGYCTGJ75G9VG4.jpg
370 ms
Athleisure_p1_l9_1_HFS125J64AF0GJ.jpg
443 ms
EcoAware_p1_l10_1_366DCB90XOM046.jpg
416 ms
WorkfromHo_p1_l11_1_HY41ZW7NAKZP44.jpg
428 ms
UniqueIdea_p1_l12_1_RBMFSFR83XR4H6.jpg
432 ms
PremierBag_p1_l13_1_LO46JZ5W461PIK.jpg
475 ms
Personaliz_p1_l14_1_U6DW49LYSL3R63.jpg
482 ms
GiveBack_p1_l15_1_DBNFIQ2QV21R39.jpg
484 ms
AwardsReco_p1_l16_1_R3HLCL0WEWX413.jpg
505 ms
Asi49427864_300x.jpg
476 ms
Asi48052055_300x.jpg
486 ms
Asi49428978_300x.jpg
500 ms
Asi305515773_300x.jpg
500 ms
2022-01-19_1512_TM98219-1_300x.jpg
505 ms
Asi48052483_300x.jpg
512 ms
Asi302864721_300x.jpg
512 ms
Asi312911683_300x.jpg
555 ms
Asi315092825_300x.jpg
524 ms
Asi49427149_300x.jpg
534 ms
Asi48052094_300x.jpg
536 ms
Asi49428419_300x.jpg
537 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff
21 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrc.woff
31 ms
fontawesome-webfont.woff
118 ms
flaticon.woff
69 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
18 ms
KFOmCnqEu92Fr1Mu4mxM.woff
26 ms
api.js
15 ms
fullline.ca accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
<frame> or <iframe> elements do not have a title
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.
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
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.
fullline.ca 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
fullline.ca SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fullline.ca 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 Fullline.ca 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.
fullline.ca
Open Graph data is detected on the main page of Full Line. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: