5.1 sec in total
712 ms
3.9 sec
526 ms
Welcome to primecard.com homepage info - get ready to check Primecard best content for United States right away, or after learning these important things about primecard.com
No coupons. No hassles. Just savings. Primecard - nation’s leading discount rewards card - The easiest way to save up to 50% on dining,retailers & travel destinations throughout South Florida & the Ne...
Visit primecard.comWe analyzed Primecard.com page load time and found that the first response time was 712 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
primecard.com performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value6.1 s
12/100
25%
Value36.2 s
0/100
10%
Value18,210 ms
0/100
30%
Value0.186
66/100
15%
Value36.7 s
0/100
10%
712 ms
106 ms
124 ms
296 ms
203 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 70% of them (69 requests) were addressed to the original Primecard.com, 10% (10 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Primecard.com.
Page size can be reduced by 284.1 kB (6%)
4.7 MB
4.4 MB
In fact, the total size of Primecard.com main page is 4.7 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 4.2 MB which makes up the majority of the site volume.
Potential reduce by 102.4 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 44.1 kB, which is 37% 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 102.4 kB or 86% of the original size.
Potential reduce by 157.5 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. Primecard images are well optimized though.
Potential reduce by 22.8 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. This website has mostly compressed JavaScripts.
Potential reduce by 1.4 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. Primecard.com has all CSS files already compressed.
Number of requests can be reduced by 43 (51%)
84
41
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Primecard. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
primecard.com
712 ms
css
106 ms
css
124 ms
global.css
296 ms
structure.css
203 ms
betheme2.css
291 ms
mfn-icons.css
344 ms
jquery-ui.css
101 ms
settings.css
346 ms
common-styles.css
384 ms
jquery-2.1.4.min.js
403 ms
jquery.browser.min.js
441 ms
js
156 ms
location.js
492 ms
js
128 ms
js
178 ms
jquery-ui.min.js
20 ms
modernizr.min.js
474 ms
mfn.menu.js
472 ms
jquery.plugins.js
682 ms
jquery.jplayer.min.js
629 ms
animations.js
682 ms
translate3d.js
682 ms
scripts.js
753 ms
jquery.themepunch.tools.min.js
888 ms
jquery.themepunch.revolution.min.js
753 ms
revolution.extension.video.min.js
887 ms
revolution.extension.slideanims.min.js
888 ms
revolution.extension.actions.min.js
1079 ms
revolution.extension.layeranimation.min.js
1086 ms
revolution.extension.kenburn.min.js
1078 ms
revolution.extension.navigation.min.js
1147 ms
revolution.extension.migration.min.js
1144 ms
revolution.extension.parallax.min.js
1146 ms
api.js
170 ms
bootstrap-modal.js
1249 ms
widget.js
161 ms
gen_204
265 ms
jquery.cookie.js
866 ms
gtm.js
292 ms
fbevents.js
295 ms
59eb3e82f30e01.png
861 ms
5e502b40ec18c8.png
2029 ms
5dd2871d5a4361.png
1153 ms
624c38a5d51de1.jpg
865 ms
5d7f733576ab61.jpg
1153 ms
5d2d66dbda2a79.jpg
1155 ms
5fc08629909910.jpg
1286 ms
62daf505ab71d0.jpg
1287 ms
62e161477a4575.jpg
1972 ms
62acd12c1d4ed0.jpg
2025 ms
62accfdf3c6477.jpg
1976 ms
62911ff39d0205.jpg
1978 ms
6282a88695f763.png
2023 ms
6282acd90516d3.png
2025 ms
6298dca82cc291.jpg
2024 ms
62b31cd1acb324.jpg
2214 ms
62570c40998681.jpg
2034 ms
624db3e2e0ea06.png
2026 ms
analytics.js
177 ms
6245d9391c9051.png
1872 ms
6219f3775ff540.png
1871 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
303 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
483 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
484 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
485 ms
KFOkCnqEu92Fr1Mu51xIIzc.ttf
486 ms
mfn-icons.woff
1933 ms
mfn-icons.woff
1847 ms
62306f990233a8.jpg
1931 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf
433 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf
434 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf
432 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf
434 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjMDrMfJQ.ttf
429 ms
480549055835001
378 ms
59ed80ffaba6a3.png
1778 ms
close-circled.png
1777 ms
why-primecard.jpg
1723 ms
discover-icon.jpg
1722 ms
swipe-icon.jpg
1722 ms
collect
229 ms
collect
208 ms
save-icon.jpg
1535 ms
easy-icon.jpg
1528 ms
party-icon.jpg
1530 ms
collect
402 ms
join-icon.jpg
1509 ms
bonus-icon.jpg
1508 ms
invite-icon.jpg
1492 ms
connect-icon.jpg
1407 ms
box_shadow.png
1406 ms
top_bar_right_shadow.png
1403 ms
box_shadow_button.png
1310 ms
yelp-star-rating.png
1116 ms
ga-audiences
820 ms
recaptcha__en.js
731 ms
ui-bg_flat_75_ffffff_40x100.png
619 ms
revicons.woff
256 ms
primecard.com 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-hidden="true"] elements contain focusable descendents
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
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
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
primecard.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
primecard.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
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Primecard.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 Primecard.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.
primecard.com
Open Graph data is detected on the main page of Primecard. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: