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.
{{url}}
{{time}} 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.
{{og_description}}
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: