Digital experiences for all disciplines
New Landing › How can we help? › Atelier › Site speed and Google page speed results
New Landing › How can we help? › Atelier › Site speed and Google page speed results
- This topic has 16 replies, 2 voices, and was last updated 7 years by David Martin – Support.
-
Posted in: Atelier
-
June 29, 2016 at 6:07 pm #278191
Hi,
I’ve done various page-speed tests and came across various improvements that I should make to improve website speed. Below are a list of things that needs to be done and various plugins that can be used to achieve them. Please guide which plugins I should use and which shouldn’t be used.
1. Above The Fold Optimization
2. Autoptimize
3. Better WordPress MinifyFurther, I would like to know which of the two cache plugins should be used for better performance with Atelier theme – W3 Total Cache or WP Super Cache ?
I’m on swift framework version 2.3.14
Thanks
June 30, 2016 at 7:02 pm #278496Hi,
I usually like using WP Super Cache as it’s a bit more simple to use. Combine that with Autoptimize and you should get a super fast site. Do not minify or combine your JS.
I’d also recommend a decent CDN, MaxCDN are decent or Cloudflare.
Thanks
June 30, 2016 at 7:48 pm #278508Thanks David,
Would do as recommended.
June 30, 2016 at 8:11 pm #278509No problem!
Cheers.July 1, 2016 at 2:23 pm #278646Hi David,
I’ve enabled cloudfront through WP Super Cache plugin. After enabling it some of the icons such as cart are no longer appearing on page. Upon inspecting the error on page this is the error
Font from origin ‘https://*****.cloudfront.net’ has been blocked from loading by Cross-Origin Resource Sharing policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. Origin ‘https://mydhaba.in’ is therefore not allowed access.
I’ve seen some posts and came through this piece of code
# ---------------------------------------------------------------------- # Webfont access # ---------------------------------------------------------------------- # Allow access from all domains for webfonts. # Alternatively you could only whitelist your # subdomains like "subdomain.example.com". <IfModule mod_headers.c> <FilesMatch "\.(svg|ttf|otf|eot|woff|woff2)$"> Header set Access-Control-Allow-Origin "*" </FilesMatch> </IfModule>
I’ve added in .htccess file, but still not able to resolve the issue. Please advice how to solve the issue.
Thanks
July 1, 2016 at 2:32 pm #278653Please your FTP details and WP login details.
– David.
July 1, 2016 at 2:48 pm #278671This reply has been marked as private.July 4, 2016 at 12:03 pm #278938Hi Kushal,
My FTP does not support that, please paste the password here.
Thanks.
July 4, 2016 at 1:22 pm #278967Hi David,
There’s no password for FTP it’s just this PPK file. The server is configured in a way that only this PPK file is required. Can you please use WinSCP to connect, it supports SCP file protocol.
Thanks
July 5, 2016 at 3:02 pm #279321Hi David,
Were you able to connect using SCP ?
Thanks
July 7, 2016 at 12:04 pm #279724No, on Mac my FTP I need a .ssh key file. Would you have this?
Thanks.
July 7, 2016 at 12:14 pm #279734This reply has been marked as private.July 7, 2016 at 12:21 pm #279738That file type has not been permitted for upload.
Do you have a cPanel file manager? We need an easier way to do this.
– David.
July 7, 2016 at 12:32 pm #279747This reply has been marked as private.July 8, 2016 at 6:54 pm #280180It looks like it’s caused by your CDN CloudFront.
It’s loading your resources, but the browser is blocking it as it thinks it’s an external unknown site.
The fix appears to be to create a DNS subdomain ex:
cdn.mydhaba.in
, then point your subdomain to your AWS Cloudfront domain.To point your subdomain to your AWS Cloudfront domain go to AWS Cloudfront control panel, select your Cloudfront distribution and enter your CDN subdomain into the Alternate Domain Names (CNAMEs) field. Something like cdn.myawesomeapp.com will do.
Now you can go to your DNS provider (like AWS Route 53) and create a CNAME for cdn.myawesomeapp.com pointing to sdf73n7ssa.cloudfront.net.
You can test your new CDN domain by making sure assets served from it are coming from Cloudfront.
Ref: http://blog.cloud66.com/cross-origin-resource-sharing-cors-blocked-for-cloudfront-in-rails/
-
Posted in: Atelier
You must be logged in and have valid license to reply to this topic.